Do you handle TLS/HTTPS termination in go code, or relly on another service (NGINX, Load Balancer, F5, Heroku, PaaS, etc)?

• certmagic

  13 4,798 7.7 Go

  Automatic HTTPS for any Go program: fully-managed TLS certificate issuance and renewal

  

I terminate SSL in GO (less moving parts to manage), and use https://github.com/caddyserver/certmagic to provision and renew my certs.

• Caddy

  401 53,568 9.4 Go

  Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS

  

Or use Caddy.

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• j8a

  1 90 8.5 Go

  j8a [ dʒʌbbʌ ] is a modern TLS 1.3 reverse proxy server designed as a lightweight API gateway for REST APIs.

TLS listening is not difficult to implement in go code as many people before have already posted. What I do like about Go's TLS server is i.e. the ability to hot-reload certificates without shutting down the listener (see: here)

Suggest a related project