While I would totally agree with this but the problem of adding a
directive would duplicate one already in R5 and is unlikely to be
syntactically compatible. So, we would need to carry forward this ugly
directive for backward compatability creating a support nightmare.
Frankly, I would leave the cache as is until we actually find out if that
is really the cause of the problem here as we discussed in the meeting.
So, yes. I would accept the refresh patch with a minor change but not the
kill the cache patch until we have concrete evidence that is causes
problems.
Andy
On Tue, 28 Apr 2020, Fabrizio Furano wrote:
> I would not disable it in an hardcoded way, as it's not clear, at least to me, whether this OpenSSL feature breaks for all use cases. For example, in DPMs this was never seen in production (the use case is different though). I would add a config parameter to selectively disable it...
>
> --
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/commit/14a693077f201e4b6a30973456008eaa23c53e2d#commitcomment-38791105
—
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/commit/14a693077f201e4b6a30973456008eaa23c53e2d#commitcomment-38791628",
"url": "https://github.com/xrootd/xrootd/commit/14a693077f201e4b6a30973456008eaa23c53e2d#commitcomment-38791628",
"name": "View Commit"
},
"description": "View this Commit 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