-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Nohacks,
On 4/30/2009 4:18 PM, nohacks wrote: > You can see from my logs that apache returns a 200 for my login page then > returns a 404 from > > It seems to be an issue now and then. It works for a while then it tosses a > 404. Maybe after a timeout I really dont know...Hard to recreate. but my > logs are full of 404 jsessionid issues... I can tell you how to recreate it: 1. Log out of your application 2. Go to the login page Result: your httpd logs are full of 404 errors for things like mystylesheet.css;jsessionid=32456789 and myloginimage.png;jsessionid=32456789. The problem is that httpd thinks the ";jsesionid" is part of the path of the resource, instead of a parameter. You can fix this either with mod_rewrite (which is a bit heavy-handed) or you can use JkStripSession On if you are using a reasonably recent version of mod_jk. Hope that helps, - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkn7UTEACgkQ9CaO5/Lv0PDwwgCcCjjHgsZI6oSDizZPpPxgMoD7 d+4An1SWaF/2Q32jyK2DiULpvPRWB4Hn =iKFe -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
