W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > January to March 2003

RE: I-D ACTION:draft-ietf-webdav-quota-01.txt

From: Clemm, Geoff <gclemm@rational.com>
Date: Tue, 25 Mar 2003 18:07:50 -0500
Message-ID: <E4F2D33B98DF7E4880884B9F0E6FDEE25ED73D@SUS-MA1IT01>
To: WebDAV <w3c-dist-auth@w3.org>

To help us in our categorization of errors, could you describe
how does a web spider responds differently to a 4xx or a 5xx?

Also, although it is good to know that one way is compliant and the
other is not (:-), it would be helpful to have some criteria to
to actually make that determination.  In particular, how do you
distinguish a client error category (making a bad request) from a
server error category (not satisfying a valid client request).
There are some obvious
cases (a syntactically ill-formed request), but many of the others
could fall in either category (the quota errors, in particular).


-----Original Message-----
From: Roy T. Fielding [mailto:fielding@apache.org]
Sent: Tuesday, March 25, 2003 4:43 PM
To: Clemm, Geoff
Cc: WebDAV
Subject: Re: I-D ACTION:draft-ietf-webdav-quota-01.txt

> What I was asking was whether there was a client that
> generically handled 4xx codes (i.e. a 4xx code that it had no
> special handling for) in a significantly different way than
> it handles a 5xx code (i.e. a 5xx code that it had no special
> handling for).

Yes, web spiders that perform maintenance.

>   I.e., when we are deciding whether to put a
> specific code in the 4xx or 5xx range, does it matter which
> one we pick?

Yes. One way is HTTP compliant; the other is not.

Received on Tuesday, 25 March 2003 18:07:57 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:27 UTC