In our case, yes, the final URL would have that form. The intention is that our redirector service has the ability to redirect clients to either caches or origins. A GET request to <redirector-domain>:443/api/v1.0/director/origin/foo/bar should redirect the client to <origin-domain>:1094/foo/bar, whereas a GET request to <redirector-domain>:443/api/v1.0/director/object/foo/bar should redirect to <cache-domain:>8443/foo/bar. The redirector knows what kind of redirection to serve based on the endpoint. I think all we would need is for the path to be appended.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/2068#issuecomment-1665652439", "url": "https://github.com/xrootd/xrootd/issues/2068#issuecomment-1665652439", "name": "View Issue" }, "description": "View this Issue 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