so, you are right, it never worked, it's just a problem that i forgot about, a problem that remained unsolved... so, the latest info it was in this issue that was tagged as solved #1060
and the basis of the issue was discussed with @apeters1971 in the following mail:

Hi,

The problem in Xrootd is not in reading it, but passing it along from redirector to the data server:

https://github.com/xrootd/xrootd/issues/1060

If the token was one-line, it wouldn't matter any more, true. But I think correctly url-encoding the parameters in Xrootd is a much simpler fix than changing the token format and propagating the new structure to all SEs and so on.

Cheers,

.costin

On 9/28/19 11:15 AM, Andreas-Joachim Peters wrote:
> The problem is XRootD.
> In EOS it works because we unescape the path+cgi ourselves inside the OFS plugin.
>
> I have to think, how to do that in a native xrootd server.
>
> Cheers Andreas.
>
>
> On Sat, Sep 28, 2019 at 9:42 AM Adrian Sevcenco <[log in to unmask] <mailto:[log in to unmask]>> wrote:
>
>     Hi! In ALICE we have a problem sending the token as an Authorization
>     header with curl (for http xrootd access). Would it be possible
>     for the
>     alicetokenacc plugin to accept tokens with stripped new-lines?
>
>     I was looking around
>     https://github.com/cern-eos/libTokenAuthz/blob/master/SealedEnvelope/TSealedEnvelope.cxx#L579
>     and https://curl.haxx.se/libcurl/c/curl_easy_unescape.html
>
>     but i did not found a solution on my own...
>
>     Can you help us somehow?
>
>     Thanks a lot!!!
>     Adrian

so, is any chance that the fixed was implemented only for TPC but not for normal access?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

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