[tahoe-dev] Fwd: [Foolscap] #150: HTTP proxy support

[duck]

Since it directly affects Tahoe-LAFS:

---------- Forwarded message ----------
From: Foolscap <trac at foolscap.lothar.com>
Date: Wed, Jan 12, 2011 at 9:55 PM
Subject: Re: [Foolscap] #150: HTTP proxy support
To:


#150: HTTP proxy support
--------------------------+-------------------------------------------------
 Reporter:  duck         |       Owner:  duck
     Type:  enhancement  |      Status:  new
 Priority:  minor        |   Milestone:  undecided
 Component:  negotiation  |     Version:  0.5.0
Resolution:               |    Keywords:  i2p http proxy transport review-needed
--------------------------+-------------------------------------------------
Comment (by duck):

 Brian's suggestion to use {{{http-proxy}}} instead of {{{httpProxy}}} has
 been taken.

 I disagree with allowing a connection to bypass this proxy for non i2p-
 addresses while the setting is given, this would allow for anonymity
 leaks.

 I disagree with calling this {{{i2p-proxy}}}, in theory this should work
 with other HTTP 1.1 proxies that support keep-alive connections (those are
 rare); except that the Banana protocol and/or the way the HTTP protocol is
 implemented in foolscap doesn't pass the HTTP parsers of a proxy like
 polipio. I consider this a to be outside the scope of this ticket.

 Unit tests as suggested by zooko have yet to be written.

--
Ticket URL: <http://foolscap.lothar.com/trac/ticket/150#comment:7>
Foolscap <http://foolscap.lothar.com>
secure remote object communication for Twisted