No subject

  According to the HTTP specification, a response code of 303 indicates that
  "the response to the request can be found under a different URI ...". It
  provides the URI where we can look for that response. It's worth noting that
  although 303 has the role of redirecting user agents after script processing
  following POST requests, the specification does not limit it to that role.

  Importantly, the specification also states that "The new URI is not a
  substitute reference for the originally requested resource." IN OTHER WORDS,
  RESPONSES CONTAINING THIS CODE DIRECT US TO RELATED MATERIAL. IF WE
  DEREFERENCE THE SUPPLIED URI AND RECEIVE A REPRESENTATION, IT IS CLEAR THAT
  THE REPRESENTATION RELATES TO THE URI WE WERE GIVEN IN THE 303 RESPONSE, AND
  NOT TO THE URI THAT LED TO THE 303 RESPONSE. IN PARTICULAR, WE'RE NOT BEING
  MISLEAD INTO THINKING THAT THE ORIGINAL URI ITSELF HAS REPRESENTATIONS.

  Of course, there is no guarantee that the URI returned in the 303 will lead to
  a representation, although often it will. We need to dereference it and react
  to the resulting response. One possibility is that the URI returned in the 303
  might itself lead to further redirections. However, if we are able, eventually
  to access a representation, we can conclude that the information is related to
  the URI that originally led to the 303 response code.

[1] http://openid.net/specs/openid-authentication-1_1.html#anchor7
[2] http://www.ietf.org/rfc/rfc2616.txt
[3] http://www.w3.org/2001/tag/doc/httpRange-14/2007-05-31/HttpRange-14.html

Thanks,

--
Noah Slater <http://bytesexual.org/>