commit 94670cb1561aa391a75e4aa4263a2dfa20b71ac2
author asanka@chromium.org <asanka@chromium.org@4ff67af0-8c30-449e-8e8b-ad334ec8d88c> Tue Nov 26 16:57:52 2013 +0000
committer asanka@chromium.org <asanka@chromium.org@4ff67af0-8c30-449e-8e8b-ad334ec8d88c> Tue Nov 26 16:57:52 2013 +0000
tree 135cde71ebadc6d8dde762e0e1e4d2b64a3ed269
parent c3e1fc7f65708a9a4c8ea9676824061d64b60292

[Downloads] Don't store or use validators unless they are strong.

ETag and Last-Modified headers shouldn't be used unless they imply
byte-wise equivalence. While RFC 2616 states that a client 'MAY' use them
anyway, we are going to be conservative and only use them if they are
strong.

BUG=7648

Review URL: https://codereview.chromium.org/67883007

git-svn-id: http://src.chromium.org/svn/trunk/src/net/tools/testserver@237349 4ff67af0-8c30-449e-8e8b-ad334ec8d88c

testserver.py

diff --git a/testserver.py b/testserver.py
index e0317e8..f028497 100755
--- a/testserver.py
+++ b/testserver.py
@@ -1478,6 +1478,8 @@
     if not self._ShouldHandleRequest('/rangereset'):
       return False
 
+    # HTTP/1.1 is required for ETag and range support.
+    self.protocol_version = 'HTTP/1.1'
     _, _, url_path, _, query, _ = urlparse.urlparse(self.path)
 
     # Defaults