> On Jun 5, 2015, at 12:07 PM, Sudheer Vinukonda
> wrote:
>
> Completely agree. Both approaches are valid and have pros and cons depending
> on how one looks at it.
> However, practically speaking, collapsing approach seems to be more
> efficient.
> The caching of intermediate redirect respo
Completely agree. Both approaches are valid and have pros and cons depending on
how one looks at it.
However, practically speaking, collapsing approach seems to be more efficient.
The caching of intermediate redirect responses against the Location cache key
(if/when they are cacheable, like Leif
> On Jun 5, 2015, at 1:47 PM, James Peach wrote:
>
>>
>> On Jun 5, 2015, at 10:45 AM, Leif Hedstrom wrote:
>>
>>
>>> On Jun 5, 2015, at 1:22 PM, Alan Carroll
>>> wrote:
>>>
>>> The chaining would only be inefficient the first time, after that the
>>> original request (that starts the cha
> On Jun 5, 2015, at 10:45 AM, Leif Hedstrom wrote:
>
>
>> On Jun 5, 2015, at 1:22 PM, Alan Carroll
>> wrote:
>>
>> The chaining would only be inefficient the first time, after that the
>> original request (that starts the chain) will just serve the cached content.
>> Even if the chain is
> On Jun 5, 2015, at 1:22 PM, Alan Carroll
> wrote:
>
> The chaining would only be inefficient the first time, after that the
> original request (that starts the chain) will just serve the cached content.
> Even if the chain is unstable as long as the final content is identical
> that's not
The chaining would only be inefficient the first time, after that the original
request (that starts the chain) will just serve the cached content. Even if the
chain is unstable as long as the final content is identical that's not a
problem.
On Friday, June 5, 2015 11:46 AM, Sudheer Vinuk
> On Jun 5, 2015, at 9:45 AM, Sudheer Vinukonda
> wrote:
>
> Below are my 2c:
>
> 1. TS-3663 tracks some caching improvements/options that you described.
>
> 3. I'm not entirely sure to agree with the chaining approach.
Agree that is is a valid approach? Or that there could ever be circumsta
Below are my 2c:
1. TS-3663 tracks some caching improvements/options that you described.
3. I'm not entirely sure to agree with the chaining approach. We have use cases
where the redirects can go as deep as 20 times (in fact, FF and Chrome IIRC
allow up to 20 redirects). I believe we set it to
Hi all,
There's been a lot of discussion on IRC about following redirects in ATS, and I
thought it might be helpful to give my thoughts on the two useful approaches
and establish some terminology. Logically, the HTTP redirects form a chain of
HTTP requests, where each link is given by the Locat
