Re: Missing something obvious with python-requests

References	<857538.2991.1357238893647.JavaMail.rgacote@Ray-iMac-2011.local> <17769250.2995.1357239221470.JavaMail.rgacote@Ray-iMac-2011.local> <mailman.71.1357268216.2939.python-list@python.org> <50e6ee72$0$6932$e4fe514c@news2.news.xs4all.nl>
Date	2013-01-05 02:24 +1100
Subject	Re: Missing something obvious with python-requests
From	Chris Angelico <rosuav@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.84.1357313079.2939.python-list@python.org> (permalink)

Show all headers | View raw

On Sat, Jan 5, 2013 at 2:00 AM, Hans Mulder <hansmu@xs4all.nl> wrote:
> It the proxy URL is http://192.168.24.25/, then the client should send
> GET requests to the proxy in both cases, and the proxy should send GET
> or CONNECT to the origin server, depending on whether origin URL uses
> SSL.
>
> If the proxy URL is https://192.168.24.25/, then the client should send
> CONNECT requests to the proxy, and the proxy should send GET or CONNECT
> as appropriate.

Are you sure? This seems backward. As I understand it, a GET request
to a proxy triggers a GET request to the origin server, and a CONNECT
request to a proxy triggers a TCP socket connection to the origin host
(which may not even be an HTTP/HTTPS server). This has nothing to do
with the protocol used between the client and the proxy.

ChrisA

Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: Missing something obvious with python-requests Chris Angelico <rosuav@gmail.com> - 2013-01-04 13:56 +1100
  Re: Missing something obvious with python-requests Hans Mulder <hansmu@xs4all.nl> - 2013-01-04 16:00 +0100
    Re: Missing something obvious with python-requests Chris Angelico <rosuav@gmail.com> - 2013-01-05 02:24 +1100

csiph-web