I can confirm with 4.10.0-rc3, which contains this PR, the observed issues are fixed (which showed up mainly in XRootD talking with dCache).
I'm still unsure whether #1002 would not have been the "better" (or rather, cleaner) implementation - @bbockelm , what's your take on this?

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

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/pull/1001?email_source=notifications\u0026email_token=AA7NRDXV5UDYXQIHJUY37SLP3ECFDA5CNFSM4HYD32S2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODX7EVUI#issuecomment-503204561", "url": "https://github.com/xrootd/xrootd/pull/1001?email_source=notifications\u0026email_token=AA7NRDXV5UDYXQIHJUY37SLP3ECFDA5CNFSM4HYD32S2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODX7EVUI#issuecomment-503204561", "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