Github user jacksontj commented on the pull request:
https://github.com/apache/trafficserver/pull/189#issuecomment-96100469
The issue comes in with clients that move between ATS boxes. For example,
if a user hits box A and gets a ticket encrypted with the newest key, its
completely possible that it will then send a request to box B which hasn't
yet recieved that newest key, meaning that we will not honor the ticket and
will force a handshake.
On Fri, Apr 24, 2015 at 12:35 PM, Bin <notificati...@github.com> wrote:
> No you don't. You just run "traffic_line -x" whenever you think they all
> have the new key. Some boxes will run "traffic_line -x" a few minutes
later
> than the others. It does not matter. The number of session tickets
> encrypted with the new key will be small. Typically one rotation cycle is
a
> few hours such as 24, or 36. A few seconds is like nothing.
>
> â
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/trafficserver/pull/189#issuecomment-96043182>.
>
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
