HTTP response code

[Recordon, David]

I SVN blame Carl and Josh. :P
 
   379     23           9/28/2006 7:33:55 PM j3h
A server receiving a properly formed request MUST send a
   380     23           9/28/2006 7:33:55 PM j3h
response with an HTTP status code of 200.
   381      8            9/5/2006 4:33:52 PM chowells
</t>
   382      8            9/5/2006 4:33:52 PM chowells
</section>
   383      8            9/5/2006 4:33:52 PM chowells

   384      8            9/5/2006 4:33:52 PM chowells
<section title="Error Responses">
   385      8            9/5/2006 4:33:52 PM chowells
<t>
   386      8            9/5/2006 4:33:52 PM chowells
If a request is malformed or contains invalid arguments,

--David

-----Original Message-----
From: specs-bounces at openid.net [mailto:specs-bounces at openid.net] On
Behalf Of Johnny Bufu
Sent: Wednesday, October 18, 2006 2:26 PM
To: specs at openid.net
Subject: HTTP response code 

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
_______________________________________________
specs mailing list
specs at openid.net
http://openid.net/mailman/listinfo/specs