Follow-up Comment #3, bug #99175 (project xrootd):
Thanks for checking; indeed I only see that the single item isn't found in
the environment (at least under the expected name), not all the subsequent
items; my apologies if you spent time trying to reproduce that part of my
report!
I think that both a client and server change would be preferable; a client
change to not send empty fields and a server change to ignore empty fields.
The client precaution means that when connecting to a current version of the
server there shouldn't be a problem, and a server side change means that a
3.2.6 client (or any other client) sending an empty field to servers in the
future won't cause the next field to be mis-named.
A release of this (and bug fix for #98997) on 3.2.x, if possible, would be
helpful for providing a fast upgrade but avoiding the step of 3.2 -> 3.3.
_______________________________________________________
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
