@abh3 Thanks for coming back to this! In fact, I have not found a workaround, but the issue has not been "pressing" enough in the past two years so I have used the XRootD protocol to access in case the individual certs had to be used.

Going back to your original questions, I think:

The restriction not to apply spacechar to = or * can be lifted — at least I don't see any way in which this would break existing use cases.
If that is in place, there's no real need to support the hash in HTTP. When using the DN directly, I think that both HTTP and XRootD should work the same, correct?
To support real-life use cases, though, a regexp matching would be required.

What do you think?

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.

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