 |
 |
Hi Cedric, The problem here is that 'xrd.port tls 1095' directive. It really only works for http because https can deal with a port already using ssl. In xroot protocol we always start off not using ssh and hen upgrade to using ssh when needed. So, there is another directive that tells the server when that should happen. Specifically, xrootd.tls https://xrootd.slac.stanford.edu/doc/dev55/xrd_config.htm#_Toc88514013 In order to always requite tls for everything use 'xrootd.tls all' and the server will tell the client it has to use tls whether the protocol is 'root' or 'roots'. If you want to be able to control it on the client side via the protocol specification then simply drop the 'tls' option of the xrd.port directive and omit the xrootd.tls directive. -- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/pull/1778#issuecomment-1242505241 You are receiving this because you are subscribed to this thread. Message ID: <[log in to unmask]> ######################################################################## 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