RE: [PATCH] Client: propfind doesn't find the correct response

[dirk . verbeeck]

> -----Original Message-----
> From: Park, Sung-Gu [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, April 24, 2001 3:03 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [PATCH] Client: propfind doesn't find the 
> correct response
> 
> > The responses are put in the hashtable by path 
> (/slide/files/a) and not by
> a
> > full href (http://localhost:8080/slide/files/a)
> 
> No.  It's dependent on servers.
> Basically, the spec is to give the href with the scheme and 
> authority part.
> But, some isn't.   This case, the server give the href as a path.
> So for the interoperability, It's required to follow the 
> server's href.
> As I've tested, it was ok with tomcat, apache and IIS 5.0
> Which server have the problem with that? I'm curious.
> If it didn't work, It's the problem.  And we should test this on that!
> 
> Sung-Gu

I'm using slide server 1.0.9 (WebdavServlet) on tomcat 3.2.1 without apache
httpd.
Here is the output of my debug session as you can see the response href is
just the path part.

Dirk

=============================================================
[LOCALHOST] /slide/files/ $ propget a a
command: propget a a
param: a
param: a
Getting properties '/slide/files/a': propfindMethod
generateQuery: <?xml version="1.0" encoding="utf-8" ?>
<D:propfind xmlns:D="DAV:"><D:prop><a/></D:prop>
</D:propfind>

Content-Length: 103
b: 103
b: <?xml version="1.0" encoding="utf-8" ?>
<D:propfind xmlns:D="DAV:"><D:prop><a/></D:prop>
</D:propfind>

responses:
<response><href>/slide/files/a</href>&#10;<propstat><prop><a>aea</a>&#10;</p
rop>
&#10;<status>HTTP/1.1 200 OK</status>&#10;</propstat>&#10;</response>

href: http://localhost:8080/slide/files/a
path: /slide/files/a
available response urls:
/slide/files/a

property: <a>aea</a>
aea
[LOCALHOST] /slide/files/ $