19 ms·

> We're not done with our request payload yet! We sent: > Host: neverssl.com > This is actually a requirement for HTTP/1.1, and was one of its big selling poi

by yfiapo 4y ago

> We're not done with our request payload yet! We sent: > Host: neverssl.com > This is actually a requirement for HTTP/1.1, and was one of its big selling points compared to, uh... > AhAH! Drew yourself into a corner didn't you. > ...Gopher? I guess? I feel like the author must know this.. HTTP/1.0 supported but didn't require the Host header and thus HTTP/1.1 allowed consistent name-based virtual hosting on web servers. I did appreciate the simple natures of the early protocols, although it is hard to argue against the many improvements in newer protocols. It was so easy to use nc to test SMTP and HTTP in particular. I did enjoy the article's notes on the protocols however the huge sections of code snippets lost my attention midway.

proto_lambda 4y ago
> I feel like the author must know this The author does know this, it's a reference to a couple paragraphs above: > [...] and the HTTP protocol version, which is a fixed string which is always set to HTTP/1.1 and nothing else. > (cool bear) But what ab- > IT'S SET TO HTTP/1.1 AND NOTHING ELSE.
- yfiapo 4y ago
  Thanks, missed that.
  - fasterthanlime 4y ago
    You know how some movie fans will sometimes pretend the sequels to some franchise don't exist? HTTP is the opposite.
    - bak3y 4y ago
      So HTTP is the old school Star Wars fans pretending the prequels don't exist?
      - HideousKojima 4y ago
        Nah it's the Buffy TV show fans ignoring the movie