In our meeting today we saw that there were cases where EBADE could be returned and cause confusion. The solution was to reword the message. We suggest:
Invalid exchange - possible authentication failure
At least that tell us it was EBADE but more likely it's an auth problem. Sort of addresses both concerns. If you change it we will approve it :-) Of course, feel free to present counter arguments.


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <xrootd/xrootd/pull/1916/c1441381815@github.com>

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