HTTP is a set of rules requesting pages from a web server and transmitting pages (including text, graphic images, sound, video, and other multimedia files) to the requesting Web browser. HTTP uses TCP ‘port 80′ . HTTP proxies can be used by Internet users to “hide” their online identity by hiding their IP (Internet Protocol) address. This might be due to the fact that some employers tend to audit what their employees have been surfing during their office hours. Indirectly, increasing users have turned to HTTP proxies to protect their anonymity for their web-surfing habits.
HTTP proxies allow users to surf the web anonymously. The user can visit any website they wish under the disguise of an anonymous IP address. HTTP also have the added benefit of typically being compatible with any kind of browser the user wishes to utilize on.
On the negative end, HTTP proxies are not always secure as they are lack of security features and often left open.
Open HTTP proxies can expose the user to even more risks In terms of piracy and frauds.
Apart from that, HTTP is a text based protocol, with all its communication pretty much readable, with no decoding, translation or decryption required. However, it is unbelievable to find that although it is advisable to encrypt to protect one’s identities, HTTP, being one of the most common used mode of transport for personal information operates almost entirely in clear text. Guess that’s because HTTP protocol was created without security in mind, but for a quick exchange of information as the key objective.
In fact HTTP can be implemented on any available TCP port but unfortunately it has become a norm to use port 80 as the standard port.
Every web browser tries to connect on that port so every web server will listed on that port, there are of course always exceptions like SSL but it is guaranteed one of the first rules a firewall administrator will put in his rule base it’s going to be ‘allow TCP 80′.