- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Sat, 18 Jan 2003 10:13:22 +0100
- To: "Julian Reschke" <julian.reschke@gmx.de>, "Lisa Dusseault" <lisa@xythos.com>, "'Clemm, Geoff'" <gclemm@rational.com>, <w3c-dist-auth@w3.org>
> From: w3c-dist-auth-request@w3.org > [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Julian Reschke > Sent: Saturday, January 18, 2003 9:22 AM > To: Lisa Dusseault; 'Clemm, Geoff'; w3c-dist-auth@w3.org > Subject: RE: PROPFIND returning *more* than expected, and other > questions > > > > > From: w3c-dist-auth-request@w3.org > > [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Lisa Dusseault > > Sent: Saturday, January 18, 2003 5:51 AM > > To: 'Clemm, Geoff'; w3c-dist-auth@w3.org > > Subject: RE: PROPFIND returning *more* than expected, and other > > questions > > > > > > > > Sorry, what's the rationale for PROPFIND not ignoring unknown XML > > elements? Does this mean anywhere in the propfind body or just in > > certain places? I assume it's supposed to fail when it sees unknown > > elements? > > ... > > Nope. PROPFIND must ignore unknown elements (hint: some servers don't...), > *except* when child of a DAV:prop or DAV:propname element. (after the morning coffee...): ...*except* when child of a DAV:prop element. -- <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Saturday, 18 January 2003 04:14:08 UTC