From: Eric Covener <covener@apache.org>
Date: Mon, 18 Jan 2016 21:14:46 +0000 (+0000)
Subject: emphasize http/1.0 clients, mention RFC7230 calling this
X-Git-Tag: 2.5.0-alpha~2392
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=a611f2cb5ec52f64158150f80cd0484cee7b1231;p=thirdparty%2Fapache%2Fhttpd.git

emphasize http/1.0 clients, mention RFC7230 calling this
envvar a SHOULD.

--This line, and those below, will be inored--

M    env.xml


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1725349 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/docs/manual/env.xml b/docs/manual/env.xml
index db8c204c7c9..f34c21fa692 100644
--- a/docs/manual/env.xml
+++ b/docs/manual/env.xml
@@ -322,12 +322,15 @@
     <section id="force-response">
         <title>force-response-1.0</title>
 
-      <p>This forces an HTTP/1.0 response to clients making an HTTP/1.0
-      request. It was originally
-      implemented as a result of a problem with AOL's proxies. Some
+      <p>This forces an HTTP/1.0 response to clients making an 
+      <em>HTTP/1.0</em> request. It was originally
+      implemented as a result of a problem with AOL's proxies during the
+      early days of HTTP/1.1. Some
       HTTP/1.0 clients may not behave correctly when given an HTTP/1.1
-      response, and this can be used to interoperate with them.</p>
-
+      response, and this can be used to interoperate with them.  Later
+      revisions of the HTTP/1.1 spec (RFC 7230) recommend this behavior 
+      for HTTP/1.0 clients.</p>
+ 
     </section>
 
     <section id="gzip-only-text-html">