On Aug 5, 2011, at 4:14 AM, Damiano ALBANI wrote:
> Regarding this last bug, I was wondering if there could a generic HTTP proxy
> mechanism, like with SOCKS, and not tied to the Web client.
> Because we might want to use an HTTP proxy for something else that Web
> traffic.
>
> What would be nice in Twisted is a generic, upper-protocol-agnostic proxy
> mechanism -- and one that would support indistinctly SOCKS and HTTP kinds of
> proxies.
You've correctly identified the status of HTTP and SOCKS proxy support in
Twisted.
However, it doesn't really make sense to have a "generic" proxy layer -
different protocols have wildly different rules about what it means to proxy a
connection. HTTP and SOCKS can proxy the same traffic and get very different
results about where that traffic goes. Similarly, it doesn't make sense to use
an HTTP proxy for anything other than HTTP traffic. If you could clarify your
request perhaps we could file a ticket? Otherwise it would be great if you
could contribute a patch to advance one of those existing tickets.
If you want a totally generic (i.e. TCP-level) proxy, Twisted does contain one:
you can run 'twistd portforward --help' for information about how to run it.
Good luck,
-glyph
_______________________________________________
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
