Print

Print

As for predicament 2: It would seem that the problem is the curl command itself and it's interaction with secretkey. Note that based on your config file, "http.selfhttps2http yes", is in effect and there was an attempt to redirect from https to http but since here was no cert, no "opaque" token was generated. That would explain the subsequent error. In general, redirection from https to http using a bearer token is not workable as the token would likely be presented again using a non-encrypted connection. Finally, I know this is only testing, but including the actual secret key in the config file is bad form as people can actually display the config file and steal the secret key.

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

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