-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Anand,
On 3/3/2009 6:59 AM, Anand HS wrote: > However, I understand that the URL rewrite mechanism ends up losing any > parameters when a HTTP POST request is sent to my domain resource. If you're issuing a /redirect/, you'll need to use the 307 response code which means "please repeat your request on this other URL, and please repeat it as a POST if the original request was a POST". See: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html > While I am right now downloading and will do a complete read up on > URLRewriter, could you give me quick heads up based on your experience of > this tool, if it handles HTTP Post request and does it preserve my > parameters. ? This is the client's job, not the server's job. If you want to /proxy/ requests (that is, have the server fetch the www.foo.com/username and return the bytes to the client) then that's a different story. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmtYVwACgkQ9CaO5/Lv0PCtewCcCiDx0i6rPR+S2ivFR/E0E85D bgAAoLZEhwBbf4HciEjKvEIFoG+H4thN =fAsp -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
