chipx86 got a fish trophy!

Summary

Force the dev server to return responses using HTTP/1.1.

Review Request #7117 — Created March 25, 2015 and submitted March 25, 2015, 4:54 p.m. — Latest diff uploaded March 25, 2015, 4:20 p.m.

Information

Owner

chipx86

Repository

Review Board

Branch

release-2.0.x

Bugs

Depends On

Commit

1414094...

Reviewers

Groups

reviewboard

People

Description

The Django dev server defaults to returning responses using HTTP/1.0 in
most cases, but this prevents Chrome from consistently working with
certain cache headers. This was discovered by some people on
StackOverflow, with this change's workaround provided.

We now force HTTP/1.1, fixing the caching problems during development.

Testing Done

I was hitting strange issues with ETags not being factored in for
subsequent requests for diffs on Chrome. This fixed it.