Hello Chris,
If you're using Tomcat (or another servlet container that supports the
JK protocol) this is quite easy to handle. First you need to set up two
virtual hosts in your Apache config, a regular host listening on port 80
and an SSL host listening on port 443. Each of those virtual hosts is
set to use mod_jk to forward to your Tomcat instance. By using mod_jk,
all of the port stuff goes away from your URLs. Apache handles all the
SSL stuff so Tomcat doesn't need to do it. And you should require no
code changes, the scheme binding will just work.
Hope that helps
Yes, I think this is very helpful !
Thank you for pointing this out. At this time, my Apache is only using
mod_proxy - I did not know how powerful mod_jk is in combination with
Tapestry :)
So when using mod_jk the parasitic port ending mentioned in my initial
posting will be gone ? Cool !
Together with Fernandos idea I now have plenty of options and keywords
to play with.
I think I will start using this mod_jk-configuration to get things done
and to accelerate the progress of my application - moving toward the
filter solution for fine grained constraints.
So kudos to you and Fernando !
Thanks again,
Gerald <- very happy now :)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
