From TheoryOrg
Jump to navigation Jump to search

Problem Connecting to tracker - HTTP Error 407 Proxy Autorization Required....

'Note: There is currently no way to do this

It would be great to add a feature so we can choose which proxy like in a browser to use with bittorent and download the files through a proxy.

BitComet works with HTTP proxies. But it is usually blocked in most Unis (HTTP CONNECT)

Using SocksCapv32 with BitTorrent it is possible to "socksify" BitTorrent using sockscap.

'socks cap doesnt work for me but i ve seen an interesting way to do it in some p2P app here it is

When client is unable to communicate with the server using plain TCP connection, HTTP tunneling can be utilized to access the Hotline server over an HTTP proxy. To accomplish this, the client creates two connections to the server. One would be used for sending, and other for receiving data. After these connections are open, the client begins transmitting standard HTTP requests. If HTTP proxy terminates connection while that connection is still in use, the client recreates them, and interrupted requests are resent.

HTTP Requests

HTTP POST request is sent over sending, while GET request is sent over receiving connection. The POST request is specified as follows:

POST <address> HTTP/1.0

Proxy-Connection: Keep-Alive

Pragma: no-cache

Host: <host>

Content-Length: 999999999

Content-Type: hotline/protocol

The server replies to this request at the time when connection is about to be closed, as:

HTTP/1.0 302 Found

Connection: close

Content-Length: 8

Content-Type: hotline/protocol

Next 8 bytes are filled with 0 to indicate termination of a connection.

GET request is specified as:

GET <address> HTTP/1.0

Proxy-Connection: Keep-Alive

Pragma: no-cache

Host: <host>

Accept: hotline/protocol

Server�s immediate reply to GET is:

HTTP/1.0 200 OK

Proxy-Connection: Keep-Alive

Content-Length: 999999999

Content-Type: hotline/protocol

After this reply, server uses this connection to send data to the client.

Address used in these requests is standard URL address followed by the session ID, specified as the file in the root directory. This is an example of such address:

Session ID is used in order to identify the client in the case of disconnect. Host name specified in the HTTP headers is in the form of standard domain name string, followed by the port number. For example:

I'm a system administrator, and I'd like to make BitTorrent available through a proxy that understands the BitTorrent protocol and can even cache requested files locally and serve them up... but of course I want to be able to control access to them as well. Is there anything like that out there? If not, one of you smart guys ought to do something about that. -- RevArgent

Back to BitTorrentFAQ
Part of [[]]

Last edit: Fri, 14 Jul 2006 13:42:10 -0700
Revisions: 17