I put up a PR with the code changes, docs, and tests.
https://github.com/apache/trafficserver/pull/4414
On Thu, Oct 11, 2018 at 1:16 PM Susan Hinrichs wrote:
> Since we will want to pull this back sooner, I'll probably have to go
> through the "backwards compatibility" pain in any case.
>
> On T
Since we will want to pull this back sooner, I'll probably have to go
through the "backwards compatibility" pain in any case.
On Thu, Oct 11, 2018 at 11:52 AM Leif Hedstrom wrote:
>
>
> > On Oct 11, 2018, at 9:23 AM, Steven R. Feltner
> wrote:
> >
> > Would this fall into the new "small, safe f
> On Oct 11, 2018, at 9:23 AM, Steven R. Feltner wrote:
>
> Would this fall into the new "small, safe feature additions" policy in the
> Slightly Modified Release Process for LTS Support, and be released in a
> forthcoming 8.x release? Or, will this have to wait for 9.0?
If it can be done
Would this fall into the new "small, safe feature additions" policy in the
Slightly Modified Release Process for LTS Support, and be released in a
forthcoming 8.x release? Or, will this have to wait for 9.0?
I like the policy vs properties breakout. Allows for a lot of extensibility as
we go
Currently there is a records.config entry,
proxy.config.ssl.client.verify.server,
which can be set to 0 (no verify), 1 (strict verify), or 2 (check but only
log).
This global setting can be overridden in the ssl_server_name.yaml file
using the verify_origin_server parameter which can be set to NO
