 |
 |
@juztas - in the end, HTTP-TPC is "simply" calling `libcurl` to do the heavy lifting while Xrootd-TPC is invoking an arbitrary executable provided by the sysadmin. In the case of HTTP-TPC, the best way to do this is through providing a unique source URL that forces things through the desired path. For Xrootd-TPC -- well, the sky's the limit. Looking at `libcurl`'s documentation, we could provide a bind interface: https://curl.haxx.se/libcurl/c/CURLOPT_INTERFACE.html Would that help here? -- 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/1192#issuecomment-630187824 ######################################################################## 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