Hi Lukasz,
Thank you for looking into this. I think Elvin and I decided that if we go
back to the redirector we start with whatever opaque information we used
on the initial go as the redirector really doesn't know (or really care)
why it is that you are arriving. I know that may not be the case for all
possible scenarios but we have to use something deterministic here andthis
approach makes sense in the general case.
Andy
On Mon, 21 Sep 2015, Lukasz Janyst wrote:
> I don't remember why I did not pass the params, but I cannot think of a good reason not to do so since any new CGI returned by the redirector will supersede the old one (on the per-variable basis). I guess it's more of a global architecture consideration. The CGI definitely should be kept when you retry at a disk server after being redirected, but you may want a "clean state" when retrying at the redirector. It's up to @abh3 to decide what he wants here :)
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/287#issuecomment-141928614
—
Reply to this email directly or view it on GitHub.
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
