5 ms·
I've never seen that in 5+ years of Go. 1) You don't have to touch Content-length since it's computed. https://golang.org/pkg/net/http/#ResponseWriter https://
by Thaxll 6y ago
I've never seen that in 5+ years of Go.
1) You don't have to touch Content-length since it's computed. https://golang.org/pkg/net/http/#ResponseWriter https://golang.org/pkg/net/http/#ResponseWriter
2) ETAGS, expire, ect ... are not managed by the std lib, as it should not.
- tyingq 6y agoOn 1), Looked, and yes, you're right, and it seems to have been there from the beginning. I think I may have been thinking of node.js on the Content-length having to be a deliberate action.