Actually, for consistency, the cadir/cafile really needs to be coordinated
with the cadir and cafile in xrd.tls directive otherwise we are just
getting a lot of confusion. Let's think about how we go about doing that!
On Thu, 18 Mar 2021, Elvin Sindrilaru wrote:
> Looks good for my side. Maybe one though would be not to mix http cadir/cafile directives with the ones used by TPC curl, since I guess the vanilla http part still needs the cadir to point to something relevant. Also another thought would be to maybe honour the **(XRDTPC_)CURLOPT_CAPATH/CURLOPT_CAFILE** env variables if they are present in the env - like this it's easier to control the TCP behavior without messing up to much with HTTP part.
>
> --
> You are receiving this because you commented.
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/pull/1431#issuecomment-801899835
—
You are receiving this because you are subscribed to this thread.
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/1431#issuecomment-802231727",
"url": "https://github.com/xrootd/xrootd/pull/1431#issuecomment-802231727",
"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