Bugzilla – Full Text Bug Listing
| Summary: | HTTPClient redirects POST actions (1GJP1U9) | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Dean Roberts <dean.t.roberts> |
| Component: | WebDAV | Assignee: | DJ Houghton <dj.houghton> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 2.0 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
PRODUCT VERSION: Eclipse 0.9 Deferring until post 2.0 [LATER->WONTFIX] The "LATER" bugzilla resolution is being removed so reopening to mark as WONTFIX. [LATER->WONTFIX] The "LATER" bugzilla resolution is being removed so reopening to mark as WONTFIX. [LATER->WONTFIX] The "LATER" bugzilla resolution is being removed so reopening to mark as WONTFIX. |
When an HTTP client receives a status response in the range 300 - 399 (inclusive) it always attempts to redirect the request (as long as the number of redirects are within the allowed range). However, this conflicts with the HTTP spec (RFC2616) and causes problems with certain server applications (such as source forge). Specifically the specification states in section 10.3: The action required MAY be carried out by the user agent without interaction with the user if and only if the method used in the second request is GET or HEAD. There is also a specific note for 303 that a POST is redirected as a GET request to facilititate login screens. There is another interesting note that 302 responses are erroneously treatede as 303 responses by allmost all existing HTTP clients and that servers may rely on this erroneous behavoiur. (This is the case with SourceForge which responds to a Login POST with a 302 and expects the client to do a redirected GET at the provided address.