title: What is the correct behavior expected of an HTTP POST => 302 redirect to GET?
body: <p>What is the correct behavior expected of a POST => 302 redirect to GET? </p>
  
  <p>In chrome (and likely most every browser), after I POST (to a resource that wants me to redirect) and I receive a 302 redirect, the browser automatically issues a GET on the 302 location. This is even a <a href="http://en.wikipedia.org/wiki/Post/Redirect/Get">well known pattern</a>. But the way I read the spec, it seems to suggest this should not happen.</p>
  
  <p><a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3">The HTTP spec says</a></p>
  
  <blockquote>
    <p>If the 302 status code is received in response to a request other than
    GET or HEAD, the user agent <strong>MUST NOT automatically redirect</strong> the
    request <strong>unless it can be confirmed by the user</strong>, since this might
    change the conditions under which the request was issued.</p>
  </blockquote>
  
  <p>And fiddler is showing: </p>
  
  <pre><code>REQUEST 1: POST URLA
  RESPONSE 1: 302 redirect to URLB
  REQUEST 2: GET URLB
  </code></pre>
  
  <p>The section above seems to say that the browser should not make the GET request? What am I missing? </p>
  
  <ol>
  <li>Something earlier in the spec that makes this section irrelevant</li>
  <li>My understanding of automatically redirect is wrong (and the chrome browser that did the GET wasn't really automatically redirecting)</li>
  <li>My understanding of confirmed this as a user</li>
  <li>Something else?</li>
  </ol>