Print

Print

Thanks a lot for testing! :-)

I guess the token isn't an arbitrary format, but should follow a key=value format (perhaps key=value&key=value, more generally).

I don't think there are any specific restrictions on the format, that said it does make sense to follow the key=value semantics as it gets chained to other ci elements

Do you have an idea which xrootd versions will have this fix? (Is it going to be back-ported?)

We plan to have 5.5.0 at the beginning of May, it could be back ported to 5.4.x if there is a strong desire ;-)

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.Message ID: <xrootd/xrootd/issues/1533/1070772988@github.com>

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1533#issuecomment-1070772988", "url": "https://github.com/xrootd/xrootd/issues/1533#issuecomment-1070772988", "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