Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
On POST creation, 201 status with a Location header should not fail #3171
In the case of a POST interaction,
In this particular case, a Location header doesn't indicate a redirection, but instead indicates the location of the created record (defined in boring detail in RFC2616, 10.2.2).
Would there be other issues I'm not seeing by also checking for an HTTP status code of 201 and not interpreting the Location header as a redirect? Even better than that, check for no status code or a
As a side note,