HTTP status codes in environment.js
getRequest in environment.js throws an exception if the http status code is anything but 200. This looks like a bug to me. It should allow any valid 2xx status code, and in particular 207:
2xx Success
The action was successfully received, understood, and accepted.
- 200 OK
- Standard response for HTTP successful requests.
- 201 Created
- 202 Accepted
- 203 Non-Authoritative Information (since HTTP/1.1)
- 204 No Content
- 205 Reset Content
- 206 Partial Content
- 207 Multi-Status (WebDAV)
- The message body that follows is anXML message and can contain a number of separate response codes, depending on how many sub-requests were made.
Jeff.
[837 byte] By [
jfish] at [2008-1-27]
Yea, The problem is that we wanted to create simple APIs for users and weren't sure how to return the status code in a way which the user could then do something usefull. For advanced users you could skip that function and make the XHTTP request directly. But you are right about 207 that doesn't make for such a sensible code to error on.
Curious to know how you encountered this error and in general would it be useful if we supported WebDAV?
Also would it be useful if we supported the more basic methods like PUT?
Just curious to understand what things users want and how they want to use them. Especially as it's something we're considering for the future as some APIs plan to expose functionality through those methods (PUT/WebDAV), the issue is most of the blocks are really about data consumption and not so much authoring. Considering we run the mashups in an anonymous context.
Thanks for the feedback!
