Tipycally i would leave the application server (tomcat, jetty) alone and
run in on port 8080 or whatever then have apache runnin on port 80 and 443.
then you configure apache ascially like this:
everything on port 80 goes to port 8080, except if it's /cart/* then
deny (or redirect to https://...:443)
everything to /cart/* on 443 redirect to 8080
This way your cart can be accesed from the end user through SSL only.
Note that it's only SSL from the client to apache, while it's in clear
between apache and tomcat but that's just a local connection so should
not be an issue.
The easiest way to have apache do this is to use mod_proxy(better) or
mod_rewrite.
If you need an example of this i probably have one somewhere :-), but
it's easy to find online too.
Nick Heudecker wrote:
This was the subject of a long discussion on IRC. At the time the
decision was to do nothing. I've been considering protecting certain
pages using mounted URLs and servlet filters, but I haven't gotten
past the consideration stage.
Eelco and Martijn might be able to weigh in on the details of that
discussion.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
