Print

Print


Hi Paul,

You are technically correct, it should not start with a '?'. The current
code simply ignores the question mark and, in fact, ignores all characters
until the first '&' (which, in itself is incorrect based on the structure
of the information. So, some adjustments would be needed here. Since the
the code treats the question mark as optional ((I assume dCache does the
same) then we should eliminate it as it will still be backward compatible.
On the other hand, keeping it would simplify allowing that the first CGI
element need not have an ampersand. Something to cogitate.

Andy


On Tue, 12 Oct 2021, Paul Millar wrote:

> The xrdcp client will generate a login token that contains various pieces of environmental information the server might find useful.
>
> For the most part, this information is serialised as key-value pairs, with `=` separating the key and value, and a `&` separating two key-value pairs. The keys are organised into a namespace, with values starting with the `xrd.` prefix.
>
> However, this information is (inexplicitly) sent as a login token with a `?` prefix.
>
> Here is an example:
>
> ```
> ?xrd.cc=de&xrd.tz=1&xrd.appname=xrdcp&xrd.info=&xrd.hostname=sprocket.desy.de&xrd.rn=v20211011-f1d4e89e2
> ```
> This is odd because a login token may also be provided by the server as part of the `kXR_redirect` response. In that response the `?` character plays a significant role in framing/serialising the response.
>
> Therefore, this looks like a mistake and the token shouldn't include the initial `?`.
>
> If so, the above login token should have been:
>
> ```
> xrd.cc=de&xrd.tz=1&xrd.appname=xrdcp&xrd.info=&xrd.hostname=sprocket.desy.de&xrd.rn=v20211011-f1d4e89e2
> ```
>
> --
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/1535


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1535#issuecomment-941198092", "url": "https://github.com/xrootd/xrootd/issues/1535#issuecomment-941198092", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

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