 |
 |
@alrossi & @paulmillar : thanks for reporting this incompatibility with dCache and for the detailed description of the problem. It is an intentional behaviour, the rational behind it is that the server might be configured to enforce encryption only for TPC orchestration: `xrootd.tls tpc`. Therefore whenever the client wants to execute a TPC, it has to open a new connection to the server indicating in the protocol request that this connection is meant for TPC orchestrating (`kXR_ExpTPC`). The server in the protocol response, in turn, will let the client know if the connection should be upgraded to TLS. At the moment I don't see other way of implementing it, other than using a separate connection for TPC orchestration. Would it be a big hassle to support this on dCache side? -- 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/issues/1359#issuecomment-742029352 ######################################################################## 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