> Hi Remy,
>
> | Modified: src/webdav/client/src/org/apache/webdav/lib/methods
> | CopyMethod.java MoveMethod.java
> | Log:
> | - Fix problems with generation of the Destination headers in COPY
> | and MOVE. For consistency with the rest of the API, all the
parameters
> in the
> | API which designate URLs are relative URLs.
>
> Let us think about the defination of relative URL.
> Notice this,
> relativeURI = net_path | abs_path | rel_path
> net_path = "//" net_loc [ abs_path ]
> abs_path = "/" rel_path
> rel_path = [ path ] [ ";" params ] [ "?" query ]
>
> RFC 2068, 2396 and 2616 can be refered above for this.
Ok. Then I was meaning absolute path.
All of the other functions of the API accept absolute paths.
Also, no server in the world would accept a request for a MOVE to another
server. Same goes with a GET on a file which would be on another server.
> IMO, how about giving the destination value of setDestination() to
> all of these case, http://xx.yy/z and /z, not even net_path.
> I mean not only /z. I think that it gives API devolper easiness.
Yes, but that is not useful here.
To move a file between servers, you should :
- Do a GET on the first server
- Do a PUT on the second server
- Do a DELETE on the first server
Remy
