Print

Print

Thanks @simonmichal

Yes, I can now see the login token being used when the client reacts to the redirection. 🎉

I've a couple of questions:

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

This isn't a problem, just something we should keep in mind if we want to pass more information this way.

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

I don't think this is a big deal. Supporting login tokens on redirection will allow us (dCache) to provide a more robust xroot protocol implementation; however, this should only matter if there are changes in how the client behaves.

Cheers,
Paul.

—
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/1069539905@github.com>

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