This setting has no affect on the ATS session cache implementation, only
the OpenSSL implementation. But you're correct in your assessment. So with
this option someone will need to force flush. This is something we plan on
exposing via a new API.
"Normally the session cache is checked for expired
On Oct 10, 2014, at 1:46 PM, bri...@apache.org wrote:
>
> +
> +.. ts:cv:: CONFIG proxy.config.ssl.session_cache.auto_clear INT 1
> +
> + This will set the OpenSSL auto clear flag. Auto clear is enabled by
> + default with ``1`` it can be disabled by changing this setting to ``0``.
>
> .. ts:c
For the record, I found out what the problem was. ATS calls the method that
generates the field twice, the first time, it wants to know the field's
size, so buf is NULL. The second time it actually wants the field's value.
(I wasn't aware of it.)
So the first time the function was called (by LogFi
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