W3C home > Mailing lists > Public > www-webdav-dasl@w3.org > January to March 2002

error reporting, was: Comments on search-00 draft

From: Julian Reschke <julian.reschke@gmx.de>
Date: Fri, 29 Mar 2002 14:44:11 +0100
To: "Lisa Dusseault" <ldusseault@xythos.com>, <www-webdav-dasl@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCCEPBEEAA.julian.reschke@gmx.de>
> From: www-webdav-dasl-request@w3.org
> [mailto:www-webdav-dasl-request@w3.org]On Behalf Of Lisa Dusseault
> Sent: Thursday, March 28, 2002 7:42 PM
> To: julian.reschke@greenbytes.de; www-webdav-dasl@w3.org
> Subject: Comments on search-00 draft
>
> ..
>
> e) Section 2.6.1 - more odd use of error responses
>
> This section specifies the use of 400 Bad Request as the error response to
> use when there is a scope problem.  I would have suggested instead 405
> Method Not Allowed if the Request-URI exists but can't handle the SEARCH
> request.  400 Bad Request can be used in so many places it's not very
> specific.
>
> Or, since your example suggests that the resources is "not found" instead,
> then the server should respond with 404 Not Found as the major response
> code.  Then it seems the body would not be required.

That wouldn't allow you to distinguish between "search arbiter not found"
and "scope not found"...

> In summary, this section seems to be unnecessarily reinventing error
> response mechanisms.

Right.

I'd propose to completely rewrite the error handling, making it
RFC3253-compatible.

> ..
Received on Friday, 29 March 2002 08:44:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 22 March 2009 03:38:08 GMT