summaryrefslogtreecommitdiff
path: root/libsoup/soup-status.c
diff options
context:
space:
mode:
authorDan Winship <danw@gnome.org>2010-04-10 12:00:58 -0400
committerDan Winship <danw@gnome.org>2010-04-10 12:16:58 -0400
commit0df6a4c66879f64bdf3ba57358e8b97c586b2387 (patch)
tree454bf7717e110ada8c602fbaf8fe426a7cacbbad /libsoup/soup-status.c
parent26c6cd984ad229a4c1d3c00889956dc0cbf53877 (diff)
downloadlibsoup-0df6a4c66879f64bdf3ba57358e8b97c586b2387.tar.gz
Fix for proxies that close the connection when 407'ing a CONNECT
If we try to CONNECT through a proxy, and it returns a "407 Proxy Authentication Required" but then closes the connection, we have to create a new connection before we can try CONNECTing again. The old soup-connection.c tunnel code did this, but it got accidentally lost in the soup-session.c version. Fix up tests/proxy-test to test both the connection-close and the persistent-connection cases. This was the underlying bug in https://bugzilla.gnome.org/show_bug.cgi?id=611663, and is at least part of https://bugzilla.gnome.org/show_bug.cgi?id=611539.
Diffstat (limited to 'libsoup/soup-status.c')
-rw-r--r--libsoup/soup-status.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/libsoup/soup-status.c b/libsoup/soup-status.c
index 11422acf..2fa309af 100644
--- a/libsoup/soup-status.c
+++ b/libsoup/soup-status.c
@@ -77,7 +77,7 @@
* @SOUP_STATUS_IO_ERROR: A network error occurred, or the other end
* closed the connection unexpectedly
* @SOUP_STATUS_MALFORMED: Malformed data (usually a programmer error)
- * @SOUP_STATUS_TRY_AGAIN: Formerly used internally. Now unused.
+ * @SOUP_STATUS_TRY_AGAIN: Used internally
* @SOUP_STATUS_CONTINUE: 100 Continue (HTTP)
* @SOUP_STATUS_SWITCHING_PROTOCOLS: 101 Switching Protocols (HTTP)
* @SOUP_STATUS_PROCESSING: 102 Processing (WebDAV)