-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 André,
On 6/22/2009 10:58 AM, André Warnier wrote: > In the "log.txt", I see that the first browser request is a POST. > The response to that is a 302 moved, with a new location. > OK so far. > But then, when the browser re-issues the request to the new location, it > does a GET, not a POST. This is common (client) reaction to a 302 response. Response codes 303 and 307 were invented to standardize the behavior of web browsers that support such codes. Unfortunately, the fear of older browsers being used has pretty much kept applications issuing 302 responses instead of the (better, IMO) 303 and 307 response codes. So, the spec has improved but the web hasn't so much. :( Nice analysis of the response, André. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAko/4rkACgkQ9CaO5/Lv0PCkVACgh4PmuOB+JLmG1Emoac3+AKwR Y0gAnjap23TcScFGxjnevhA++xwetvF8 =b8Ef -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
