Follow-up Comment #4, bug #99283 (project xrootd):
If it is like that, maybe one should reject invalid file names already on
client side and on server side or replace special problematic characters
automatically like done in standard URL encoding.
We had problems with users creating filenames which are a hell to reproduce
on a shell, so we decided to exclude all kind of escape sequences and special
characters in EOS ... but space is actually still one of the easier to handle
- therefore not forbidden.
_______________________________________________________
Reply to this item at:
<http://savannah.cern.ch/bugs/?99283>
_______________________________________________
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
