Allow chrome to handle 407 auth challenges to CONNECT requests

jingle/notifier/base/proxy_resolving_client_socket.cc

Index: jingle/notifier/base/proxy_resolving_client_socket.cc
===================================================================
--- jingle/notifier/base/proxy_resolving_client_socket.cc	(revision 117986)
+++ jingle/notifier/base/proxy_resolving_client_socket.cc	(working copy)
@@ -172,7 +172,9 @@
   // Now that we have resolved the proxy, we need to connect.
   status = net::InitSocketHandleForRawConnect(
       dest_host_port_pair_, network_session_.get(), proxy_info_, ssl_config_,
-      ssl_config_, bound_net_log_, transport_.get(), connect_callback_);
+      ssl_config_, bound_net_log_, transport_.get(), connect_callback_,
+      base::Bind(&ProxyResolvingClientSocket::OnNeedsProxyTunnelAuthCallback,
+                 base::Unretained(this)));
   if (status != net::ERR_IO_PENDING) {
     // Since this method is always called asynchronously. it is OK to call
     // ProcessConnectDone synchronously.
@@ -180,6 +182,14 @@
   }
 }
 
+void ProxyResolvingClientSocket::OnNeedsProxyTunnelAuthCallback(
+    const net::HttpResponseInfo& response_info,
+    net::HttpAuthController* auth_controller,
+    net::CompletionCallback callback) {
+  // TODO(rch): figure out what to do here

[cbentzel, 2012/01/18 12:14:22]

Do you want to figure this out prior to landing this CL?

[akalin, 2012/01/19 21:07:37]

so I tried to trace through what 'regular' sockets do and as far as I can tell
it ends up calling HttpNetworkTransaction::OnNeedsProxyAuth.  This client socket
is used for XMPP connections (used by sync and cloud print) and so there's no
HTTP transaction at all (I assume that HttpNetworkTransaction refers to the
'real' HTTP connection and not possibly the HTTP proxy).

So in Chrome, whenever proxy auth is needed for a web page it pops up a window
asking for credentials, right?  We've never supported that for sync
(http://crbug.com/19581), and I think doing so would require thinking through
the UI flow (since users may be confused by sync popping up an auth dialog when
there's no visible web page).

So, short answer, I think we can 'fail' here, or do whatever it used to do
before this change.

[Ryan Hamilton, 2012/01/19 23:11:19]

Done.

[Ryan Hamilton, 2012/01/19 23:11:19]

Done.

+  callback.Run(net::OK);
+}
+
 void ProxyResolvingClientSocket::ProcessConnectDone(int status) {
   if (status != net::OK) {
     // If the connection fails, try another proxy.