Replace nonsense statement in the backport proposal (the backport has

  merit, but for an altogether different reason).

  http2-wg has no impact on HTTP/1.1 protocol, and Upgrade: request and
  response in this case is defined by the HTTP/1.1 RFC, alone.  An Upgrade
  header in an HTTP/2.0 stream is entirely under the scope of HTTP/2.0 RFC.

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1741098 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/STATUS b/STATUS
index eb1fc85a21edcb34f2a7e4b3156c251675851d01..affdafaf3cd142fc57737ba40c63572a25ccb9ae 100644 (file)
--- a/STATUS
+++ b/STATUS
@@ -118,12 +118,12 @@ PATCHES ACCEPTED TO BACKPORT FROM TRUNK:
 PATCHES PROPOSED TO BACKPORT FROM TRUNK:
   [ New proposals should be added at the end of the list ]
 
-  *) Suppress 'h2' announcements in Upgrade: header as declared illegal by
-     http-wg.
+  *) Suppress 'h2' announcements in Upgrade: header as such Upgrade: requests
+     are not honored by mod_http2. 
      trunk patches: http://svn.apache.org/r1740075
                     http://svn.apache.org/r1740119
      2.4.x: trunk works modulo CHANGES
-  +1: icing
+     +1: icing
      
   *) mod_proxy_hcheck: Dynamic reverse proxy backend health check module
      Trunk version of patch: <various>