[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Open Questions on using the Atom Feed Format for search results


On Sep 28, 2005, at 3:37 PM, Darrick Brown wrote:

My concern is not the error codes themselves.  I'm concerned with what
error codes get returned when.  I agree that the Atom spec should not
duplicate Section 10 of RFC2616.  However, Atom has new concepts that
HTTP does not.


Not unless APP somehow screwed itself.  AFAIK, APP is a
subset of HTTP/1.1.

For example, what error should I expect back from an APP
server if I PUT an updated Entry to a previously existing entry URI that
has since been deleted? 

You'll have to be a little more specific than that.  If you did
a normal PUT and you have authorization, the response should be 200
(no error there).  If you did a conditional PUT with If-Match, then
2616 requires the response to be 412 (Precondition Failed):

   If none of the entity tags match, or if "*" is given and no current
   entity exists, the server MUST NOT perform the requested method, and
   MUST return a 412 (Precondition Failed) response. This behavior is
   most useful when the client wants to prevent an updating method, such
   as PUT, from modifying a resource that has changed since the client
   last retrieved it.

I don't see how 2616 could be any clearer than that.

Should I expect "400 Bad Request", "404 Not
Found", or "406 Not Acceptable"?  2616 certainly does not cover this.


None of those codes are applicable to your situation, so I'm not
sure your question makes any sense.  2616 does "cover this".

....Roy