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

Re: Status Code/Entity body encoded in XML

From: Julian Reschke <julian.reschke@gmx.de>
Date: Tue, 04 Nov 2003 21:35:20 +0100
Message-ID: <3FA80D88.7030707@gmx.de>
To: Stanley Guan <stanley.guan@oracle.com>
Cc: w3c-dist-auth@w3.org

Stanley Guan wrote:

> See comments in line!
> 
> Thx,
> 
> -Stanley
> 
>>Stanley Guan wrote:
>>
>>  <snip>
>>
>>1) PROPFIND never returns a 200 code.
> 
> 
> How do you come up with the conclusion?  What section of the
> spec. says about it?

Possibly none. If this is the case, it should be fixed.


>>2) If a method returns 207, the content type MUST be */xml, and the 
>>response must have a DAV:multistatus root element.
>>
>>3) Servers *may* return a */xml response for 4xx and 5xx status codes, 
>>in which case a client can test for a DAV:error root element or a 
>>DAV:multistatus element to extract more information.
> 
> 
> Does the only status codes that servers may return a */xml response include
> only:
>     4xx, 5xx, and 207?

Servers MAY return */xml on any request. However, the spec only 
specifies what this means for 207, 4xx and 5xx.


Julian


-- 
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Tuesday, 4 November 2003 15:35:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:44:05 GMT