From: Fabian Frank <fabian@pagefault.de>
Date: Wed, 5 Feb 2014 08:21:16 +0000 (-0800)
Subject: http2: rely on content-encoding header
X-Git-Tag: upstream/7.37.1~641
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=133cdd29ea059f6596b387878ce3bc60d501c798;p=platform%2Fupstream%2Fcurl.git

http2: rely on content-encoding header

A server might respond with a content-encoding header and a response
that was encoded accordingly in HTTP-draft-09/2.0 mode, even if the
client did not send an accept-encoding header earlier. The server might
not send a content-encoding header if the identity encoding was used to
encode the response.

See:
http://tools.ietf.org/html/draft-ietf-httpbis-http2-09#section-9.3
---

diff --git a/lib/http.c b/lib/http.c
index 2ea6f7e..9ce216e 100644
--- a/lib/http.c
+++ b/lib/http.c
@@ -3402,7 +3402,8 @@ CURLcode Curl_http_readwrite_headers(struct SessionHandle *data,
 
     }
     else if(checkprefix("Content-Encoding:", k->p) &&
-            data->set.str[STRING_ENCODING]) {
+            (data->set.str[STRING_ENCODING] ||
+             conn->httpversion == 20)) {
       /*
        * Process Content-Encoding. Look for the values: identity,
        * gzip, deflate, compress, x-gzip and x-compress. x-gzip and
diff --git a/lib/http2.c b/lib/http2.c
index baf36cc..a4baca9 100644
--- a/lib/http2.c
+++ b/lib/http2.c
@@ -410,7 +410,6 @@ CURLcode Curl_http2_request_upgrade(Curl_send_buffer *req,
   free(base64);
 
   k->upgr101 = UPGR101_REQUESTED;
-  k->auto_decoding = GZIP;
 
   return result;
 }
@@ -641,7 +640,7 @@ int Curl_http2_switched(struct connectdata *conn)
   httpc->data = NULL;
   httpc->datalen = 0;
 
-  conn->data->req.auto_decoding = GZIP;
+  conn->httpversion = 20;
 
   /* Put place holder for status line */
   Curl_add_buffer(httpc->header_recvbuf, "HTTP/2.0 200\r\n", 14);