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

Re: Status Code/Entity body encoded in XML

From: Stanley Guan <stanley.guan@oracle.com>
Date: Tue, 4 Nov 2003 12:23:00 -0800
Message-ID: <009901c3a311$7135ab20$c5b42382@us.oracle.com>
To: "Julian Reschke" <julian.reschke@gmx.de>
Cc: <w3c-dist-auth@w3.org>

See comments in line!

Thx,

-Stanley

----- Original Message ----- 
From: "Julian Reschke" <julian.reschke@gmx.de>
To: "Stanley Guan" <stanley.guan@oracle.com>
Cc: <w3c-dist-auth@w3.org>
Sent: Tuesday, November 04, 2003 10:44 AM
Subject: Re: Status Code/Entity body encoded in XML


> 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?

> 
> 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?

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

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