On 04/09/2006, at 7:30 PM, James Ellis wrote:
The RFC for this is at ftp://ftp.isi.edu/in-notes/rfc2616.txt via
http://www.w3.org/Protocols/#Specs which includes the available codes
in the Spec.
Yep though its a shame that within a given domain the status code
definitions are so vague that
On 05/09/2006, at 11:37 AM, Matthew Cruickshank wrote:
Is there any convention or standard for this?
Not that I've found. The Yahoo's web services API documentation
says that 400: Bad request. The parameters passed to the service
did not match as expected which seems about right for missing
Tim Lucas wrote:
Any RESTafarians around?
Yep, I've got a REST interface for my conversion software.
Is there any convention or standard for this?
Not that I've found. The Yahoo's web services API documentation says
that 400: Bad request. The parameters passed to the service did not
match
Any RESTafarians around?
I'm implementing a REST API and am wondering if there's a standard /
standard practice / strong opinion on what HTTP status codes map to
form validation errors when processing HTTP REST requests.
Say for example I have the following HTTP request:
POST
