> On Mar 27, 2018, at 9:52 PM, Persia Aziz <persia.a...@yahoo.com> wrote:
>
>
> @Leif,
>
> Yes, this is for certificated loaded via plugin. I don't know of any such API
> to hand a new context to ATS. Again, looking at the code, the ocsp is enabled
> on a context only at the initialization phase. So any context created
> externally in a plugin does not get configured with the global ATS
> configuration.
This is way outside my area of expertise, but it seems we already have
tsapi TSSslContext TSSslServerContextCreate(void);
So why can’t we setup the OCSP default callback handler in that existing API?
Having two APIs each doing part of the context “initialization” seems
unnecessary. Heck, even if we needed to add new parameters to
TSSslServerContextCreate() that would be fine, since we can break API / ABI
compatibility in v8.0.
Cheers,
— Leif
