Rob,
Do you have any metric that points to which browsers do or do not
support a 201 Created status / Location header combination? I'd be
interested in knowing as I'm having a hard time finding a definitive
answer to this question.
Regardless of client method, my experience has been this has worked fine
for me on newer browsers (probably since FF 1.0 and IE 5. maybe since
decent XmlHttpRequest support has existed?). Granted, I don't test wide
across very many browsers.
I am under the assumption that the super majority of user agents support
this, and to downgrade, one could always specify a message body in the
response (like a one line "click here" URL, or a quick javascript redirect).
To discourage people from using 201 Created with a Location header is,
well, discouraging.
Adam
Rob Heittman wrote:
Yes, except many user agents only understand 201 Created in response to a
PUT, not a POST. Again, a lot depends on whether the server facility is
being written for general browsers or a specific client. The Location
header is also used in the 303 See Other response.
On 12/10/07, Ben <[EMAIL PROTECTED]> wrote:
Isn't this where the "Location" HTTP header should be used, to indicate
the URL
of the new resource?
