 |
 |
Hi @mpatrascoiu - In the case you outline, we benefit from the fact that HTTP is more network-friendly than GridFTP. The latter would send one side of the transfer an IP address and had to make an educated guess of whether the remote side could speak IPv6 (or not). In HTTP, the 'client' typically gets a hostname which it can resolve to an IP address using its own resolution rules. That allows the IPv4-only site to implement IPv4-only transfers via managing the hostname lookups (e.g., gai.conf) -- no help from FTS should be needed! The downside of the request is that someone uses it in production, sets it, forgets about it, and causes transfers to be permanently pinned to IPv4 for the rest of our lifetime. Since the use case is pretty targeted, has an alternate workaround if needed, and has a potentially large downside, I'm reluctant to go down this route. -- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/1472#issuecomment-1265405868 You are receiving this because you commented. 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