Thursday, October 9, 2014, 10:39:01 PM, you wrote:
> On Oct 9, 2014, at 6:08 PM, Shu Kit Chan wrote:
>> It seems to be similar to this jira ticket -
>> https://issues.apache.org/jira/browse/TS-1463
> Yeah, Kit is spot on. This is a known problem with the plugin, and it’s an
> artifact of how
+1
Thanks,
-Igor
On Fri, Oct 10, 2014 at 10:32 AM, Jared Ocker wrote:
> That would be fantastic. If there¹s anything we can do to help expedite
> the open sourcing, please let me know. This has definitely been a pain
> point for us.
>
> Thanks,
> .: Jared
>
> On 10/9/14, 8:48 PM, "Sudheer Vin
That would be fantastic. If there¹s anything we can do to help expedite
the open sourcing, please let me know. This has definitely been a pain
point for us.
Thanks,
.: Jared
On 10/9/14, 8:48 PM, "Sudheer Vinukonda"
wrote:
>Hi Leif and all,
>
>Just fyi, We have an enhanced version of the plugi
Hi Leif and all,
Just fyi, We have an enhanced version of the plugin, that we use internally
that works around these limitations and is able to serve the stale copy to
successive requests until a fresher copy is available.
We may work on open sourcing that version soon, if time permits.
Thank
> On Oct 9, 2014, at 8:39 PM, "Leif Hedstrom" wrote:
>
>
>> On Oct 9, 2014, at 6:08 PM, Shu Kit Chan wrote:
>>
>> It seems to be similar to this jira ticket -
>> https://issues.apache.org/jira/browse/TS-1463
>
> Yeah, Kit is spot on. This is a known problem with the plugin, and it’s an
> a
On Oct 9, 2014, at 6:08 PM, Shu Kit Chan wrote:
> It seems to be similar to this jira ticket -
> https://issues.apache.org/jira/browse/TS-1463
Yeah, Kit is spot on. This is a known problem with the plugin, and it’s an
artifact of how the ATS cache works. To be able to implement
stale-while-re
It seems to be similar to this jira ticket -
https://issues.apache.org/jira/browse/TS-1463
Kit
On Thu, Oct 9, 2014 at 3:53 PM, Jared Ocker wrote:
> We have the stale-while-revalidate plugin in place and have noticed some
> behavior that seems suboptimal. While cache is fresh, everything works
We have the stale-while-revalidate plugin in place and have noticed some
behavior that seems suboptimal. While cache is fresh, everything works great.
The first page hit after our 300sec s-maxage has passed comes back with
“Warning: 110 Response is stale” as expected. However, it appears to b
