profind method bug

[Henrik Holst]

tor 2010-09-23 klockan 02:05 +0100 skrev Joe Orton:
> On Mon, Aug 02, 2010 at 05:48:08PM +0900, Jong Gyu Lee wrote:
> > Hi.
> > I'm Jong-Gyu Lee.
> > I think there is a bug in neon.
> > I cound not access http://box.net/dav with neon.
> > I found that after requesting a profind method the response according to it
> > is wrong.
> > So I modified neon library like the attached patch file.
> > Before making sure the attached patch file, you need to check HTTP
> > request/response message with WireShark.
> > I wish that this mail gives you a helping hand.
> 
> Can you give an example of a PROPFIND request body which is malformed?  
> The ne_propfind_* code uses a root element of:
> 
> <propfind xmlns="DAV:">
> 
> which means it is not necessary to declare and use the "D" namespace as 
> your patch does (unless I'm missing a case where the default DAV: 
> namespace is not declared with ne_propfind_*).

I agree with Joe here, this seams like an error on the server side, i.e
who ever wrote the server software at box.net didn't implement proper
namespace handling in their XML codes and instead probably thought that
the entities should be named "<D:prop>".

This is a common misconception with custom webdav servers. D: does not
stand for WebDAV, it's simple the most used form, one could as easily
send data as:

<propfind xmlns:Q="DAV:">
<Q:prop>...</Q:prop>

Which would be a proper request, but I assume that box.net would fail
with that request as well.

We use propfinds extensively with neon and have yet to see a malformed
request.

/Henrik Holst