Disable chunked encoding for HTTP server responses

Question

I'm writing a small experimental http server in GO using the net/http package, and I need all my replies to have 'identity' transfer encoding. However the http server in GO always returns responses using the 'chunked' transfer. Is there any way to disable chunked encoding on HTTP server in GO?

One thread in golang-nuts touches ths topic: groups.google.com/d/topic/golang-nuts/3sYwQlUOv-o/discussion — zzzz
– zzzz, Commented Jan 14, 2013 at 8:54
Thanks @Tom! There was a typo in the Content-Length header string. This fixed everything :) — Dany
– Dany, Commented Jan 14, 2013 at 9:06

laslowh · Accepted Answer · 2013-01-15 14:12:38Z

2

It's not clear to me whether responding with "Transfer-Encoding: identity" is valid under the spec (I think maybe you should just leave it out), but...

Inspecting the code here, I see this inside the WriteHeader(code int) function (it's a little bit strange, but this function actually flushes all the headers to the socket):

367     } else if hasCL {
368         w.contentLength = contentLength
369         w.header.Del("Transfer-Encoding")
370     } else if w.req.ProtoAtLeast(1, 1) {
371         // HTTP/1.1 or greater: use chunked transfer encoding
372         // to avoid closing the connection at EOF.
373         // TODO: this blows away any custom or stacked Transfer-Encoding they
374         // might have set.  Deal with that as need arises once we have a valid
375         // use case.
376         w.chunking = true
377         w.header.Set("Transfer-Encoding", "chunked")
378     } else {

I believe "hasCL" in the first line above refers to having a content length available. If it is available, it removes the "Transfer-Encoding" header altogether, otherwise, if the version is 1.1 or greater, it sets the "Transfer-Encoding" to chunked. Because this is done right before writing it to the socket, I don't think there's currently going to be any way for you to change it.

edited Jan 15, 2013 at 14:12

answered Jan 14, 2013 at 21:50

laslowh

8,6345 gold badges36 silver badges45 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

Dany Over a year ago

Adding Content-Length does the trick. (I got a typo in that header). Thanks!

Timmmm Over a year ago

But what if you don't know the content length?

MrMesees Over a year ago

@Timmmm then nobody should talk to your client / proxy because it is poorly designed to follow a problematic part of HTTP1.1 which HTTP2 removed

Collectives™ on Stack Overflow

Disable chunked encoding for HTTP server responses

1 Answer 1

3 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related