Forum Discussion
Ben_95489
Oct 05, 2010Nimbostratus
Hey Blake,
I suspect that this is related to the general problems with User-Agents processing 301 and 302 statuses for POST requests. The expected behavior can be found in RFC 2616 ( http://datatracker.ietf.org/doc/rfc2616/ ) Sections 10.3.2 and 10.3.3. To quote:
10.3.2
"If the 301 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.
Note: When automatically redirecting a POST request after receiving a 301 status code, some existing HTTP/1.0 user agents will erroneously change it into a GET request"
What is the redirect for? (i.e. HTTP to HTTPS?) In some cases it may actually be better to use a stream profile to rewrite the page content as it is delivered to the user-agent so that a redirect is no longer actually required.
Cheers!
// Ben