summaryrefslogtreecommitdiff
path: root/misc/dashboard
diff options
context:
space:
mode:
authorBrad Fitzpatrick <bradfitz@golang.org>2013-03-29 20:25:11 -0700
committerBrad Fitzpatrick <bradfitz@golang.org>2013-03-29 20:25:11 -0700
commit2a91051f843f7449b5ff0cea49a7865cc16d0c82 (patch)
treecd9526cc974e644dfe137244eb6cb2822e482863 /misc/dashboard
parent9a03bbb22c842fae25af564b1942eb9917d06148 (diff)
downloadgo-2a91051f843f7449b5ff0cea49a7865cc16d0c82.tar.gz
net/http: ignore 100-continue responses in Transport
"There are only two hard problems in computer science: cache invalidation, naming things, and off-by-one errors." The HTTP server code already strips Expect: 100-continue on requests, so httputil.ReverseProxy should be unaffected, but some servers send unsolicited HTTP/1.1 100 Continue responses, so we need to skip over them if they're seen to avoid getting off-by-one on Transport requests/responses. This does change the behavior of people who were using Client or Transport directly and explicitly setting "Expect: 100-continue" themselves, but it didn't work before anyway. Now instead of the user code seeing a 100 response and then things blowing up, now it basically works, except the Transport will still blast away the full request body immediately. That's the part that needs to be finished to close this issue. This is the safe quick fix. Update Issue 3665 R=golang-dev, dsymonds, dave, jgrahamc CC=golang-dev https://codereview.appspot.com/8166045
Diffstat (limited to 'misc/dashboard')
0 files changed, 0 insertions, 0 deletions