Author cameron
Recipients cameron
Date 2010-01-25.04:33:59
SpamBayes Score 2.01546e-06
Marked as misclassified No
Message-id <1264394042.86.0.571652227077.issue7776@psf.upfronthosting.co.za>
In-reply-to
Content
I'm trying to do HTTPS via a proxy in Python 2.6.4 (which is supposed to incorporate this fix from issue 1424152).

While trying to debug this starting from the suds library I've been reading httplib.py and urllib2.py to figure out what's going wrong
and found myself around line 687 of httplib.py at the _tunnel()
function.

_tunnel() is broken because _set_hostport() has side effects.

_tunnel() starts with:
  self._set_hostport(self._tunnel_host, self._tunnel_port)
to arrange that the subsequent connection is made to the proxy
host and port, and that is in itself ok.

However, _set_hostport() sets the .host and .port attributes in
the HTTPConnection object.

The next action _tunnel() takes is to send the CONNECT HTTP command,
filling in the endpoint host and port from self.host and self.port.
But these values have been overwritten by the preceeding _set_hostport()
call, and so we ask the proxy to connect to itself.

It seems to me that _tunnel() should be grabbing the original host and port before calling _set_hostport(), thus:

  ohost, oport = self.host, self.port
  self._set_hostport(self._tunnel_host, self._tunnel_port)
  self.send("CONNECT %s:%d HTTP/1.0\r\n\r\n" % (ohost, oport))

In fact the situation seems even worse: _tunnel() calls send(), send() calls connect(), and connect() calls _tunnel() in an infinite regress.
- Cameron Simpson
History
Date User Action Args
2010-01-25 04:34:02cameronsetrecipients: + cameron
2010-01-25 04:34:02cameronsetmessageid: <1264394042.86.0.571652227077.issue7776@psf.upfronthosting.co.za>
2010-01-25 04:34:00cameronlinkissue7776 messages
2010-01-25 04:33:59cameroncreate