Join GitHub today
net/http: server links in crypto/tls when not serving TLS #30483
What version of Go are you using (
You can learn why with:
But I'm not sure this is a priority. Even if we did the games to make the linker happy enough to be able to drop things, that only helps the Server. We'd have to play the same games with the http.Transport code (as used by the http.Client) and basically you'd have to never use the http.Client or http.Transport types anywhere in your code, or ever import net/http/httputil.ReverseProxy (which uses Transport), etc, because the Transport doesn't know until runtime whether you're going to use https or not.
Actually, considering the line above:
This is basically impossible to fix.
It's also been like this since day 1.