Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(811)

Unified Diff: net/spdy/spdy_proxy_client_socket.cc

Issue 4935001: Allow a non-200 (or non-407) response for a CONNECT request from an HTTPS pro... (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src/
Patch Set: Cleaned up Created 10 years ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: net/spdy/spdy_proxy_client_socket.cc
===================================================================
--- net/spdy/spdy_proxy_client_socket.cc (revision 68026)
+++ net/spdy/spdy_proxy_client_socket.cc (working copy)
@@ -105,7 +105,7 @@
}
bool SpdyProxyClientSocket::IsConnectedAndIdle() const {
- return IsConnected() && !spdy_stream_->is_idle();
+ return IsConnected() && spdy_stream_.get() && !spdy_stream_->is_idle();
vandebo (ex-Chrome) 2010/12/04 00:30:37 Why did this change?
Ryan Hamilton 2010/12/09 21:19:35 Bug, actually. Removed.
}
void SpdyProxyClientSocket::SetSubresourceSpeculation() {
@@ -355,8 +355,10 @@
if (response_.headers->response_code() == 200)
return OK;
+ else if (response_.headers->response_code() == 407)
+ return ERR_TUNNEL_CONNECTION_FAILED;
else
- return ERR_TUNNEL_CONNECTION_FAILED;
+ return ERR_HTTPS_PROXY_TUNNEL_CONNECTION_RESPONSE;
}
// SpdyStream::Delegate methods:

Powered by Google App Engine
This is Rietveld 408576698