Closed GoogleCodeExporter closed 9 years ago
Original comment by an.delb...@gmail.com
on 3 Apr 2013 at 8:25
What you say it's true for HttpsMapper, ehich is used in
RequestMapperApplication. But if you try to set CryptoMapper as root mapper
AFTER mounting a page to a specific path, this last won't work (i.e. the
mounted page won't be served at the specific path). Try to use the following
code in a quickstart project:
public void init()
{
super.init();
//pages and resources must be mounted after we have set CryptoMapper
mountPage("/foo/", HomePage.class);
setRootRequestMapper(new CryptoMapper(getRootRequestMapper(), this));
}
HomePage path will be encrypted and not plain '<app path>/foo'
Original comment by an.delb...@gmail.com
on 5 Apr 2013 at 10:42
You're completely right! I missed the whole point of using CryptoMapper which
is to encrypt NON-mapped page paths and leave mapped page paths alone.
In my case, I needed to build a "true" root mapper which receives all requests
(like HttpsMapper) and I used section 8.6.6 as an example. This obviously
didn't work as I intended for the reasons outlined above, but I didn't stop to
think that things are different for CryptoMapper.
Sorry for the confusion!
Original comment by berni...@gmail.com
on 5 Apr 2013 at 3:10
Original comment by an.delb...@gmail.com
on 5 Apr 2013 at 3:27
Original issue reported on code.google.com by
berni...@gmail.com
on 3 Apr 2013 at 3:16