I just realized this: Is this really a problem with libXrdHttpVOMS, or libXrdHttp?
I think this is the main point here. While the discussion also taking via mail is definitely needed and in the long-term, joining all the efforts is surely the way to go, all issues currently discussed here are likely issues in libXrdHttp
and just worked around / "hidden" in the XrdLCMAPS
plugin (as @bbockelm pointed out in #1177 (comment) ). So the bug fixing in XRootD should not be hindered by this ;-).
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
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