Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #31216
| Path | csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!feeds.phibee-telecom.net!newsfeed.xs4all.nl!newsfeed6.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail |
|---|---|
| Return-Path | <rosuav@gmail.com> |
| X-Original-To | python-list@python.org |
| Delivered-To | python-list@mail.python.org |
| X-Spam-Status | OK 0.044 |
| X-Spam-Evidence | '*H*': 0.91; '*S*': 0.00; 'deny': 0.07; 'get.': 0.09; 'https': 0.09; 'path.': 0.09; 'server,': 0.15; 'from:addr:rosuav': 0.16; 'from:name:chris angelico': 0.16; 'hehe...': 0.16; 'knock': 0.16; 'localhost': 0.16; 'oct': 0.16; 'proxy,': 0.16; 'wrote:': 0.17; 'requests': 0.18; 'mostly': 0.20; 'supposed': 0.21; 'http': 0.22; 'permitted': 0.22; 'seems': 0.23; 'header:In-Reply-To:1': 0.25; 'looks': 0.26; 'am,': 0.27; 'easiest': 0.27; 'message- id:@mail.gmail.com': 0.27; 'correct': 0.28; 'origin': 0.29; 'normally': 0.30; 'code': 0.31; 'getting': 0.33; 'right?': 0.33; 'to:addr:python-list': 0.33; 'received:google.com': 0.34; 'server': 0.35; 'similar': 0.35; 'received:209.85': 0.35; 'there': 0.35; 'except': 0.36; 'but': 0.36; 'client': 0.36; 'test': 0.36; 'subject:http': 0.37; '(for': 0.37; 'received:209': 0.37; 'subject:: ': 0.38; 'instead': 0.39; 'to:addr:python.org': 0.39; 'little': 0.39; 'header:Received:5': 0.40; 'your': 0.60; 'address': 0.60; 'most': 0.61; "you'll": 0.62; 'respect': 0.63; 'more': 0.63; 'direct': 0.69; 'receive': 0.71; 'acts': 0.71; 'obvious': 0.71; 'alone,': 0.84; 'happier': 0.84; 'memories': 0.84; 'ports': 0.93 |
| DKIM-Signature | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=4XjGRTj8y6IhkZSGewWgQ/QLel8tj1g8ceX9JLRdfBc=; b=GCGyo09RVMlGsWHZq13uX8HJwbiYnvLOxV0u1D+NpdHl5E62LsGju8fCqT6nVZJ5RT WDWoB8X1B7dB/Vngo/+ddEqvHhQgdH3PHX16Ul0C5RHcCu4IdAABeaT2uQItX3/M/ARM iQtdl5ypJYHj/gftC64I5IindRCAtoQGyGoTK+dwc8KYjZBlumnlOscWITG4Db6Z4XI7 rcqN8mW1cHe4GQZ1/7Ej5N7gr53innxlu0pGxfxcda0OnmcQPOh6FKM7BdYX8Vug9JLt q3scabMH0dkwaxUSQRc5vmPkTHF1o1UVvGlATpX/b4ICPu30r/CNq/FsHTPdhkRWHFZg dBKw== |
| MIME-Version | 1.0 |
| In-Reply-To | <20121013204358.6d400240@pcolivier.chezmoi.net> |
| References | <20121013204358.6d400240@pcolivier.chezmoi.net> |
| Date | Sun, 14 Oct 2012 05:50:31 +1100 |
| Subject | Re: Understanding http proxies |
| From | Chris Angelico <rosuav@gmail.com> |
| To | python-list@python.org |
| Content-Type | text/plain; charset=ISO-8859-1 |
| X-BeenThere | python-list@python.org |
| X-Mailman-Version | 2.1.15 |
| Precedence | list |
| List-Id | General discussion list for the Python programming language <python-list.python.org> |
| List-Unsubscribe | <http://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe> |
| List-Archive | <http://mail.python.org/pipermail/python-list/> |
| List-Post | <mailto:python-list@python.org> |
| List-Help | <mailto:python-list-request@python.org?subject=help> |
| List-Subscribe | <http://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.2134.1350154234.27098.python-list@python.org> (permalink) |
| Lines | 21 |
| NNTP-Posting-Host | 2001:888:2000:d::a6 |
| X-Trace | 1350154234 news.xs4all.nl 6959 [2001:888:2000:d::a6]:39429 |
| X-Complaints-To | abuse@xs4all.nl |
| Xref | csiph.com comp.lang.python:31216 |
Show key headers only | View raw
On Sun, Oct 14, 2012 at 5:43 AM, Olive <diolu@bigfoot.com> wrote: > it seems when I read the code above that the proxy acts mostly as an > orinary server with respect to the client except that it is supposed to > receive the full URL instead of just the path. Am I right? Is there any > documentation on what an http proxy is supposed to implement. The easiest way to test this is to knock together a quick little server, set your browser to use localhost as a proxy, and see what requests you get. You're correct as regards most requests, but HTTPS is more complicated. All your proxy will see is a CONNECT request; you have to accept or deny on the basis of address alone, you don't get the whole URL (for obvious reasons). But that aside, yes, you'll normally get a request that looks pretty similar to what the origin server would get. ahh, happy memories of MUDding through a local proxy that permitted CONNECT on more ports than 443... and even happier memories of getting port 23 opened to direct access, hehe... ChrisA
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Understanding http proxies Olive <diolu@bigfoot.com> - 2012-10-13 20:43 +0200 Re: Understanding http proxies Chris Angelico <rosuav@gmail.com> - 2012-10-14 05:50 +1100 Re: Understanding http proxies Tim Roberts <timr@probo.com> - 2012-10-14 12:58 -0700 Re: Understanding http proxies Cameron Simpson <cs@zip.com.au> - 2012-10-15 11:57 +1100 Re: Understanding http proxies Olive <diolu.remove_this_part@bigfoot.com> - 2012-10-15 09:53 +0200
csiph-web