I don’t normally comment, but feel like I need to chime in here.
I agree in keeping with the stack behavior. This change has the potential to
break a lot of plugin logic and will cause a lot of work across many dev teams
that maintain many plugins. The pristine URL should be used in subsequent
ir and VP of the Apache Traffic Server project;
> > Bryan Call!
> >
> > Cheers,
> >
> > — leif
> >
> >
>
--
Bret Palsson | https://cobook.co/bretep
t; cool. We should come with an agreement on this, such that the workflow is
> well defined.
>
> — Leif
>
>
--
Bret Palsson | https://cobook.co/bretep
I sent a response on Aug 12. Here was what I sent. Are my messages being
moderated? I'm not seeing the email in the archives.
https://mail-archives.apache.org/mod_mbox/trafficserver-dev/201508.mbox/browser
-- Forwarded message --
From: Bret Palsson
Date: Wed, Aug 12, 2015 at
e TLS session.
>
> > If it can’t be overridable, would it make sense to have an API as well
> for this? Such that a plugin can set the session keys, which would then let
> you manage the rotation in any way that you seem fit.
>
> It would be great to have more flexibility i
we discussed the need for this and my view is still that it is
> not necessary. Reloading the SSL configuration should be completely
> harmless and it seems very straight forward for the job that populates the
> new keys to call traffic_line at the right time.
>
> cheers,
> James
--
Bret Palsson | https://cobook.co/bretep
It doesn’t take long to get a good idea of what the
> status is.
> >
> >
> > Finally, I’d ask everyone to consider joining the issues@trafficserver
> mailing list, and monitor new and resolved Jira’s, as well as general build
> errors from Jenkins.
> >
> > Sincerely,
> >
> > — leif
> >
>
>
--
Bret Palsson | https://cobook.co/bretep
