Tim, Unfortunately the patch does not achieve the stated goal. > It's great that you guys are trying to follow the RFC, but the problem is, > what we really need is a client that can act like a web browser, not something > that strictly follows the RFC.
No sane browser I know of blindly redirects POST requests to a new location. What a browser is supposed to do having received a redirect status code in response to a POST request is to issue a <strong>GET</strong> request to the redirect URL. The REAL problem is that currently HttpClient design has a serious design flaw: HttpMethod interface represents both request and response making these two entities tightly coupled. As a side effect HttpClient simply cannot issue an additional request(s) behind the scene and present the result to the user if though it was the response of the original request. We are well aware of the problem http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21584 but its resolution will require a complete design overhaul and I do not see this coming any time sooner than release 3.0. Meanwhile the problem is really easy to work around by having a little bit if code around HttpClient that takes care of those redirects that could not be handled automatically. For details see HttpClient's redirect guide below: http://jakarta.apache.org/commons/httpclient/redirects.html Cheers Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
