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.
The HTTP protocol was never written with security in mind and should not be thought of a bad because it doesnâEUR(TM)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.