Https Server with a single insecure/http endpoint? Share your thoughts.

Question

Hello!

I'm wondering if it is possible to create a Golang https server with a single insecure endpoint on which one could handle certificate request etc? (Without creating another server for this endpoint in particular)

Aditya Agrawal · Accepted Answer

I'm assuming you want to expose your Go service to the network directly, and don't have a load balancer/reverse proxy/... in front of your backend infrastructure. Like mentioned before, key exchange is a low-level detail that's handled before high-level request interpretation (such as parsing the request path) is handled. You can therefore not decide whether TLS is required based on the request path/URL. What you can do is expose two different ports and require TLS on one of them. This is sometimes useful to do, e.g. for providing a health check for probing. Here's an example that exposes one secure port and one insecure port. This example should be fairly straight forward (remember to always wrap your handlers in a http.Server, especially when the requests go straight to your Go service without any LB/reverse proxy in front): https://play.golang.org/p/yWSFLM6s1Qj

Owen Williams · Answer

Yes, create a second Lister on a different port with the handler to the endpoint you want to serve.

Go Language

Similar Discussions

Gophers, what parts of Go did you find/are you finding challenging to learn?

Periodically running a go web-scraper?

Go modules and Google cloud, having trouble in renning code!

On a mission to build Next-Gen Community Platform for Developers

Facebook

Twitter

Linkedin

Instagram