From 153d31da1629facdc855ad0e4e91369ec2124ac7 Mon Sep 17 00:00:00 2001
From: Emmanuel Odeke <emm.odeke@gmail.com>
Date: Sun, 19 Jun 2016 17:30:29 -0700
Subject: [PATCH] doc/go1.7.html: net/http RFC 2616 conformation +
 timeoutHandler on empty body

- Mention RFC 2616 conformation in which the server now only sends one
"Transfer-Encoding" header when "chunked" is explicitly set.
- Mention that a timeout handler now sends a 200 status code on
encountering an empty response body instead of sending back 0.

Change-Id: Id45e2867390f7e679ab40d7a66db1f7b9d92ce17
Reviewed-on: https://go-review.googlesource.com/24250
Reviewed-by: Andrew Gerrand <adg@golang.org>
---
 doc/go1.7.html | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/doc/go1.7.html b/doc/go1.7.html
index 0acfb6c8fc..105e3b4eab 100644
--- a/doc/go1.7.html
+++ b/doc/go1.7.html
@@ -855,6 +855,16 @@ so that <code>w.WriteHeader(5)</code> uses the HTTP response
 status <code>005</code>, not just <code>5</code>.
 </p>
 
+<p>
+The server implementation now correctly sends only one "Transfer-Encoding" header when "chunked"
+is set explicitly, following <a href="https://tools.ietf.org/html/rfc2616#section-3.6">RFC 2616</a>.
+</p>
+
+<p>
+In the server, a 200 status code is sent back by the timeout handler on an empty
+response body, instead of sending back 0 as the status code.
+</p>
+
 <p>
 In the client, the
 <a href="/pkg/net/http/#Transport"><code>Transport</code></a> implementation passes the request context
-- 
2.48.1