HTTP-Tunnel Client

HTTP-Tunnel Client is a program created by HTTP-Tunnel Corporation that masks application data as HTTP traffic to bypass firewalls. This is done by routing all outgoing traffic through port 80, the standard HTTP traffic port, and encapsulating this inside HTTP packets. Since almost all firewalls allow HTTP traffic to pass through, the masked application is allowed to communicate with remote hosts. HTTP-Tunnel uses encryption to maintain transfer security.

In order to mask application traffic with HTTP-Tunnel, the application must implement the SOCKS protocol. This protocol is implemented in several Peer-to-Peer clients, internet browsers, instant messaging applications, and other programs.

Usage

HTTP-Tunnel Corp is a company with array of products, one of which allows firewall blocked applications to send and receive data from the internet. The firewall blocking the application must be on the side of the HTTP-Tunnel user, and not on that of the remote host.

HTTP-Tunnel creates a tunnel -just as its name says- between the user's computer and the outer side of the user's firewall. Currently, HTTP-Tunnel offers a free service for low bandwidth. Paid server you can receive about 400KB a sec. But this depends on your location to their servers and your network speed. Other key word services for HTTP-Tunnel Client are: Bypass firewall, secure browsing, Hide your IP, Socks, HTTP, Tunneling, anonymous browsing, proxy.

These are some common reasons for using HTTP-Tunnel:

  • Need to bypass any firewall
  • Need secure internet browsing
  • Need to use favorite programs with out being monitored by work, school, ISP or government.
  • Extra security for online transactions
  • Encrypt Internet traffic.
  • Need to play online games
  • Visit sites that you were previously blocked from accessing
  • Prevent 3rd party monitoring or regulation of your Internet browsing and downloads
  • Use your favorite applications previously blocked
  • Hide your IP address

How IT Works

Mediator servers

HTTP-Tunnel uses mediator servers in order to maintain the tunnel. The HTTP-masked application data travels from the user's machine to the mediator servers. From that point, the data is converted into the original application traffic (the one the user's application understands) and forwarded to the remote host.

From the remote host's viewpoint, the traffic seems to come from the mediator servers.

Masking and routing process example

In the following example, we will say a HTTP-Tunnel user called "Adam" has a program named "application X". Thiks by connecting to a remote server called "application X server". Because Adam works in a firewalled office, application X's traffic is GeneRally blocked, thus preventing the program from connecting to application X server.

The remote host will believe HTTP-Tunnel mediator servers sent the data. Because of this, every time the remote host wants to reply, it will do so sending data to HTTP-Tunnel mediator servers.

See also

  • Proxy server
  • Tunneling protocol
  • Bypass firewall
  • Secure internet
  • Monitor free

See Also

Interactive application security testing