I was afraid of that. It might also be https not cleaning up the error
queue but you should have seen https errors as well if there were any to
clean up. Anyway, I pushed to master a small change to always clear the
error stack after authentication completes so that the thread is not
carrying any unwanted garbage. I was hoping Matevz would coordinate,
perhaps with you, to test it on one of the servers, He, perhaps
fortuantely, seems to have taken some time off.
Andy
On Wed, 2 Jun 2021, jthiltges wrote:
> We are indeed running xrootd with https.
>
> --
> You are receiving this because you modified the open/close state.
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/pull/1464#issuecomment-853548844
—
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/pull/1464#issuecomment-853553459",
"url": "https://github.com/xrootd/xrootd/pull/1464#issuecomment-853553459",
"name": "View Pull Request"
},
"description": "View this Pull Request 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