3839RE: [rest-discuss] 403 vs. 409
- Aug 4, 2003
> From: David Powell [mailto:djpowell@...]So you think this is wrong because WebDAV added a new status code? I can't
> Sent: Monday, August 04, 2003 9:08 AM
> To: firstname.lastname@example.org
> Subject: Re: [rest-discuss] 403 vs. 409
> Saturday, August 2, 2003, 9:36:07 AM, you wrote:
> >> WebDAV defines a "422 Unprocessable entity" status for semantic
> >> problems with the XML request, and uses 400 if the XML request is not
> >> properly formed. I don't see why WebDAV would be a special case here,
> >> so that sounds wrong too.
> > Could you please explain why you think this is wrong?
> I just don't think that it is a WebDAV specific problem, so I would
> expect WebDAV to use whatever status would be appropriate for any
> other HTTP application.
agree -- the whole point of WebDAV is to *extend* HTTP/1.1 (with new
methods, request headers...), and therefore adding a new specific 4xx status
code because none of the existing ones fitted well seems to be absolutely
right thing to do.
> I tend to favour 400, but it looks as if 422 was invented for WebDAVJulian
> because it was decided that 400 couldn't be used to report errors that
> weren't strictly syntactic?
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
- << Previous post in topic Next post in topic >>