> I'm also using the 1.0.9 client but there isn't any difference I think,
> here is the relevant part of the code.
> The cvs version has the following line
> Enumeration enum = method.getResponseProperties(href);
> and my fix was to change it to
> Enumeration enum = method.getResponseProperties(path);
>
> In my last mail you can see that href
(http://localhost:8080/slide/files/a)
> isn't in the response but path (/slide/files/a) is.
>
<response><href>/slide/files/a</href> <propstat><prop><a>aea</a> </p
> rop> <status>HTTP/1.1 200 OK</status> </propstat> </response>
>
> I looked at the spec and I think both formats are valid.
Indeed, both are correct (that mirrors HTTP/1.1).
> It's just strange that the Slide Server is sending relative path and the
> client is expecting absolute URIs.
Most of the WebDAV servers return relative paths. I also like relative paths
better.
> So my patch isn't correct, is just makes the slide server work.
>
> And the spec doesn't say you cannot use .. in the URI so that href search
> algorithm will become
> a little more complex than a simple lookup :-)
Remy
