Possible bug mod_dav 1.0.2

Hi,

I was doing interop tests and encountered the following problem:

a) Set a dead property with no namespace, for instance by:

<propertyupdate xmlns="DAV:">
	<set>
		<prop>
			<bar xmlns="">123</bar>
		</prop>
	</set>
</propertyupdate>

This works, no error is reported.

b) A PROPFIND however returns XML formatted like this:

<D:multistatus xmlns:D="DAV:">
<D:response xmlns:ns0="DAV:" xmlns:ns1=""  xmlns:lp0="DAV:"
xmlns:lp1="http://apache.org/dav/props/">
	<D:href>/test/UTF8.TXT</D:href>
	<D:propstat>
		<D:prop>
			<bar>123</bar>
			<lp0:creationdate>2001-08-08T12:14:01Z</lp0:creationdate>
			<lp0:getcontentlength>32</lp0:getcontentlength>
			<lp0:getlastmodified>Wed, 08 Aug 2001 12:14:01 GMT</lp0:getlastmodified>
			<lp0:getetag>"c5077-20-3b712d09"</lp0:getetag>
			<lp1:executable>F</lp1:executable>
			<D:supportedlock>
				<D:lockentry>
					<D:lockscope><D:exclusive/></D:lockscope>
					<D:locktype><D:write/></D:locktype>
				</D:lockentry>
				<D:lockentry>
					<D:lockscope><D:shared/></D:lockscope>
					<D:locktype><D:write/></D:locktype>
				</D:lockentry>
			</D:supportedlock>
			<D:lockdiscovery/>
			<D:resourcetype/>
			<D:getcontenttype>text/plain</D:getcontenttype>
		</D:prop>
		<D:status>HTTP/1.1 200 OK</D:status>
	</D:propstat>
</D:response>
</D:multistatus>

Note the invalid namespace declaration xmlns:ns1="", which is correctly
rejected by MSXML and AElfred (Saxon), but sadfully accepted by Xerces [1].
Also note that the prefix isn't actually used in the property, so maybe this
can easily be fixed by not creating the namespace declaration at all.

[1] <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3040>

Received on Thursday, 9 August 2001 06:26:11 UTC