I’ve added a dummy TLS implementation to be used when neither OpenSSL nor BoringSSL are selected, providing only the APIs actually used by Pingora. This is a step towards solving two issues:
Pingora currently cannot compile without TLS support, yet sometimes an HTTP-only server is sufficient.
Someone aiming to provide another TLS implementation (e.g. #29) has no way of knowing which parts of the vast OpenSSL API actually have to be reproduced.
This at least gets Pingora to compile with --no-default-features. It will still fail at startup because it attempts to initialize some TLS connectors, some more work is required here. Also, quite a few tests rely on TLS being available – these probably need to run conditionally.
I’ve added a dummy TLS implementation to be used when neither OpenSSL nor BoringSSL are selected, providing only the APIs actually used by Pingora. This is a step towards solving two issues:
This at least gets Pingora to compile with
--no-default-features. It will still fail at startup because it attempts to initialize some TLS connectors, some more work is required here. Also, quite a few tests rely on TLS being available – these probably need to run conditionally.