There are quite a few problems with HTTP like you cannot parse it
because the grammer allows anything, most importantly:

- Multiple HTTP Accept Headers (with empty entries) allowed
- Newline or Carriage Return or both or whatever

Because of this great flexibility you can enjoy undeterministic
responses from different web servers and agents.

Also consider common use:
IP
TCP (state)
HTTP (stateless)
HTTP Cookies (state) <- seriously?

To make matters worse there are HTTP-Only-Cookies for people who cannot
properly escape their code in the backend and have to abuse HTTP for
protecting them (probably brought to you by the same people calling NAT
a security feature).

Reply via email to