 |
 |
OK, I see the issue. The token can be used in either CGI context or CURL context. I agree that '+' is not valid in CURL context (the standard says so). The standard also says % escape and '+' are both valid in CGI context. So, we really do not have a good path forward except to add '+' should the token be used in CURL context (i.e. TPC). If the Alice plug-in for XRootD supports both (does it?), then we should just say '+' should not be used to make the forward path consistent. On Thu, 12 Nov 2020, Elvin Sindrilaru wrote: > Currently XrdHttp does not support decoding '+' to empty string bUT only % encoded values: > https://github.com/xrootd/xrootd/blob/master/src/XrdHttp/XrdHttpUtils.cc#L319 > > Of course, if XrdHttp will add support for '+' decoding then this will work. But then we'll also need to remove the calls to curl_escape/curl_unescape which also don't decode '+' to empty space. I guess curl_* can be regarded as the "golden standard" when it comes to handling encoded info. > > -- > You are receiving this because you commented. > Reply to this email directly or view it on GitHub: > https://github.com/xrootd/xrootd/issues/1320#issuecomment-726017653 -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/1320#issuecomment-726322147 ######################################################################## 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