Is there anything in the README that's not in the docs? Can we nuke it?
On Oct 8, 2014, at 9:16 PM, zw...@apache.org wrote:
> Repository: trafficserver
> Updated Branches:
> refs/heads/master ae573e94e -> b4529fd61
>
>
> Make README be consistent with official Docs as well as code.
>
>
> Pro
I thought you were going to format to our style guidelines before committing?
On Oct 8, 2014, at 11:34 AM, bri...@apache.org wrote:
> Repository: trafficserver
> Updated Branches:
> refs/heads/master 195259b16 -> f1bedb41e
>
>
> TS-3080: Optimized SSL Session Cache
>
>
> Project: http://git-
On Oct 7, 2014, at 2:58 PM, Jon Sime wrote:
> Per the Documentation Roadmap, I've been putting together notes for a
> new style guide. The primary goals being improvements to consistency,
> quality, and readability for the docs. I've included, after receiving
> some initial feedback, the updated
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
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
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
> 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
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
