在不使用内容长度的情况下禁用 go 中的分块传输编码
[英]Disable chunked transfer encoding in go without using content-length
问题描述
Is there a way to disable chunked transfer encoding in go without using a content-length?
有没有办法在不使用内容长度的情况下禁用 go 中的分块传输编码？
It's for Server-Sent Events which can't have either.它适用于服务器发送的事件，两者都没有。
1 个解决方案
解决方案1
3 2016-01-14 16:42:55
将传输编码标头设置为标识：
w.Header().Set("Transfer-Encoding", "identity")
声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.
相关问题
“内容长度”或“分块传输编码”是 Http 请求的必要条件吗？ - Is “Content-Length” or “chunked transfer-encoding” a must for Http request?
分块编码和内容长度标头 - Chunked encoding and content-length header
内容长度标头与分块编码 - Content-Length header versus chunked encoding
HTTP内容长度和分块传输编码。 有2GB的限制吗？ - HTTP Content-Length and Chunked Transfer-Encoding. Is there a 2GB Limit?
net/http 服务器不发送 100 Continue 除非客户端发送 Transfer-Encoding: chunked or nonzero Content-Length - net/http server does not send 100 Continue unless client sends Transfer-Encoding: chunked or nonzero Content-Length
即使未在http请求中设置content-length标头，我的HTTP响应也没有分块传输编码 - My HTTP response does not have transfer-encoding chunked even after not setting content-length header in http request
如何处理没有 Transfer-Encoding 和 Content-Length 标头的请求消息？ - How to treat request messages without Transfer-Encoding nor Content-Length headers?
如果没有Content-Length或Transfer-encoding，对GET请求的HTTP响应会发生什么？ - What happens in HTTP response to a GET request without Content-Length or Transfer-encoding?
HTTP响应头有效，没有Transfer-Encoding和Content-Length？ - HTTP response headers valid with no Transfer-Encoding and Content-Length?
RFC 2616 HTTP内容长度和传输编码兼容性 - RFC 2616 HTTP Content-Length and Transfer-Encoding Compatibility
相关标签