You are viewing a plain text version of this content. The canonical link for it is here.
Posted to slide-dev@jakarta.apache.org by di...@the-ecorp.com on 2001/04/24 13:33:02 UTC

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

Applies against
jakarta-slide\src\webdav\client\src\org\apache\webdav\util\WebdavResource.ja
va

The responses are put in the hashtable by path (/slide/files/a) and not by a
full href (http://localhost:8080/slide/files/a)

 <<propfind.patch>> 


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

Posted by "Park, Sung-Gu" <je...@thinkfree.com>.
----- Original Message -----
From: <di...@the-ecorp.com>
To: <sl...@jakarta.apache.org>
Sent: Tuesday, April 24, 2001 8:33 PM
Subject: [PATCH] Client: propfind doesn't find the correct response


> Applies against
>
jakarta-slide\src\webdav\client\src\org\apache\webdav\util\WebdavResource.ja
> va
>
> 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