Davide Bianchi wrote:
It started out a bit simpler sticking to proxy... Where as mod_jk had changes two places both in tomcat and http.Nino Saturnino Martinez Vazquez Wael wrote:Hmm, well because I'd like the configuration to be simple (which it arent really now). And wanted it to be at apache HTTP configured not a mix of HTTP and tomcat.. So no real arguments, I guess I could change it. However the only thing bothering me now are cookies. So if the only way are mod_jk i'll have to take that i guess?I'm not completely sure if the cookie problem is generated by the proxy module or not, the proxy directives should simply 'route' the connection to tomcat and back, I was just wondering the reason to stick to a proxy configuration where a mod_jk one would have been much simpler.
If I connect directly to tomcat, I do get my cookies. It's the same with jetty, which Im using for development. So it seems that it's probably my configuration of the proxy module thats lacking something. I just wonder what im doing wrong.But if you connect directly with Tomcat (by using the :8080 port in the URL) and have no trouble with the cookies bit, I suppose the problem does lies in the proxy module.
Davide
-- -Wicket for love Nino Martinez Wael Java Specialist @ Jayway DK http://www.jayway.dk +45 2936 7684 --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|