HTTP response code

Johnny Bufu johnny at sxip.com
Wed Oct 18 18:26:20 UTC 2006


I was reviewing draft 10 to make sure our implementation complies  
with all MUSTs, and I believe I've spotted an issue with the wording  
in sections 5.1.2.1 and 5.1.2.2, specifically:

"5.1.2.1.  Successful Responses

A server receiving a properly formed request MUST send a response  
with an HTTP status code of 200.

5.1.2.2.  Error Responses

If a request is malformed or contains invalid arguments, the server  
MUST send a response with a status code of 400."

Given that any message is either properly formed or malformed (and  
nothing beside), the two MUSTs above cannot be satisfied in the case  
of a properly formed message, but containing invalid arguments.

Draft 9 had the wording as "valid request" vs "malformed or  
containing invalid arguments" (sections 6.1.2.1 and 6.1.2.2).


Thanks,
Johnny



More information about the specs mailing list