Free Articles, Free Web Content, Reprint Articles
Monday, May 28, 2012
 
Free Articles, Free Web Content, Reprint ArticlesRegisterAll CategoriesTop AuthorsSubmit Article (Article Submission)ContactSubscribe Free Articles, Free Web Content, Reprint Articles
ADVERTISEMENTS
 

Anonymous Browsing And The Difficulties Of HTTP

This article will briefly outline the main reason why browsing anonymously is not able to supported through the HTTP protocol.

HTTP is a basically the methods through which your browser communicates with any website and exchange information but there are many problems within the protocol that restricts anonymity like the fact that it exists on the TCP port 80.

Port 80 has become a standard TCP port to use and almost every web server will list that port with the exception of security such as SSL but as a general rule most connection are through the TCP port 80. Firewalls will usually allow all TCP80 communications as a first rule. The protocol itself is text based ASCII to be precise which means that all communication must be readable this means no translation, decryption or decoding. It is quite bad easy to follow a HTTP trace and if you ignore all the GET requests/responses you can pretty much read the rest which is bad when we are told to protect and be secure with our personal information.

HTTP treats every request and response as individual questions and answers this means it cannot follow long or draw out complicated conversations. Even when the communication comes from the same place HTTP will treat the information as a totally separate thing. HTTP also suffers a severe lack of security and does not authenticate users. Through the use of cookies HTTP can get round some of the authentication issues by maintaining a connected state between the sever and the client there can also be protocols such as NTLM and certain forms and services like Microsoft Passport.

The HTTP protocol was never written with security in mind and should not be thought of a bad because it doesn’t have security features, it was designed for the quick exchange of information in a simple manner it does this jobs really well otherwise it would not have survived the rate in which the internet is expanding and developing.

Clearly HTTP cannot be anonymous as it is designed to exchange passwords, usernames and identities the same way as all of the information it transfers and it cannot protect your information or identity even when HTTP just blocks your IP address this is not really achieving any anonymity.

Source: Free Articles from ArticlesFactory.com

ABOUT THE AUTHOR


Oliver is a passionate security analyst who likes to advertise the correct ways to safeguard corporate websites. Oliver works for SSL 247 who specialise in cheap SSL cert as well as IIS SSL certificate for web servers in the UK.



Health
Business
Finance
Travel
Home Repair
Technology
Computers
Family
Communication
Entertainment
Autos
Marketing
Self Help
Sports
Home Business
Education
ECommerce
Law
Other
Internet
Partners


Page loaded in 0.057 seconds