The bottom line is that the front end should be able to supply some kind of authorization information if you said it should. We are quite strict about that on the XRootD side. It appears the http side is a bit laissez faire about it. I don't subscribe to laissez faire security. There is a middle ground as I said. But at the very least one of the plugins has to succeed.

—
You are receiving this because you commented.
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/1236#issuecomment-652916011", "url": "https://github.com/xrootd/xrootd/issues/1236#issuecomment-652916011", "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