We have observed kXR_mv requests with a source path like:
//foo/my-file?xrd.gsiusrpxy=/opt/domatests/x509up&xrd.wantprot=gsi,unix
This kind of construction is allowed for kXR_Open, see:
http://xrootd.org/doc/dev49/XRdv400.htm#_Toc517297859
However, my reading of the kXR_mv suggests that this isn't allowed:
http://xrootd.org/doc/dev49/XRdv400.htm#_Toc517297858
However, such requests are succeeding when given to the SLAC xrootd server, with the server stripping off this opaque/query part and processing the kXR_mv request as if the source path has no query part.
Either the xrootd protocol allows the client to specify opaque/query part in the kXR_mv source path or it does not.
If the xrootd protocol allows an opaque part in the kXR_mv source path, could the protocol documentation be updated to reflect this?
If the xrootd protocol does not allow the kXR_mv source path to have an opaque part, could the xrootd clients be updated so they do not send it.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/xrootd/xrootd/issues/850
########################################################################
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
