-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tore,
Tore Eriksson wrote: > The reason for the client > not acting on the redirect is that sendRedirect does not send any > Content-length header, and the client will then wait for an eventual > Content body until the servlet finishes. This could be avoided if the > sendRedirect would include "Content-length: 0" in its HTTP headers. Although this technique works, it shouldn't be necessary. The Content-Length header is not required by HTTP for server responses (or the client requests for that matter). The client should accept this situation and take appropriate action, rather than getting confused ;) Nice to know that there was a solution, even if it is kind of a hack. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkj9QXcACgkQ9CaO5/Lv0PBLbQCeK1uytfY2eQ+TvY9d6HFD2xoo yysAni+P+WHY76wPP3SEMf4utp9inemj =BQbQ -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
