You are correct that the spec does not explicitly state the encoding. However, it is implied in http://xrootd.org/doc/dev42/XRdv300.htm#_Toc414892705 with the conclusion that paths are plain old ASCII with certain characters outlawed. By implication, it would include non-ASCII characters. I must admit we have gone ying and yang over this and current implementation does not fully enforce this (which some people like and some do not). Technically, a path should be rejected as described in the above section. We have never gotten any request to support more than this. If we get a significant desire we could add it; but that seems unlikely given how people interpret paths. --- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/333#issuecomment-183205487 ######################################################################## 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