URL:
<http://savannah.cern.ch/bugs/?99175>
Summary: different behavior of xrdcp in 3.3rc1 with redirect
opaque data
Project: XROOTD
Submitted by: dhsmith
Submitted on: 2012-11-30 11:57
Report Type: Bug
Priority: 5 - Normal
Severity: 3 - Normal
Status: None
Privacy: Public
Assigned to: None
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Fixed by commit(s):
_______________________________________________________
Details:
In 3.3rc1; on redirect for write with opaque data like:
&item=abc&item2=def
xrdcp goes to the redirect target server with opaque data like
oss.asize=123&&item=abc&item2=def
The double ampersand causes the loss of the extra query items in the "opaque"
section, at the server.
It could be that the original redirecting server was not supposed to put the
initial ampersand, but the deployed dpm-xrootd instances are all doing this;
so it would not be good to have a client that breaks with it.
(Actually I'd put the initial ampersand in the redirect because I thought it
was needed, I'd noticed an occasion where the 3.2.x client wasn't adding the
ampersand between two adjacent items on retry; but I didn't report it,
perhaps it was a bug)
Cheers,
David
_______________________________________________________
Reply to this item at:
<http://savannah.cern.ch/bugs/?99175>
_______________________________________________
Message sent via/by LCG Savannah
http://savannah.cern.ch/
########################################################################
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
