Print

Print

Predicament 1: I understand now the point, many thanks. I am not really sure how to proceed on this though. I was planning to exploit the "fast unencrypted data access" using both http.selfhttps2http and http.secretkey. Any advice?
Regarding xrootd "restarting", this was my guess since from /afs/cern.ch/user/r/rdimaria/public/xrootd.log-xrootdticket-davix_escape-nosecretkey it can be seen a new XCache initialisation after the request.

However, I am still puzzled by the fact that using a CMS cert with 1 attribute hides this issue.

—
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-658048127", "url": "https://github.com/xrootd/xrootd/issues/1251#issuecomment-658048127", "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