5 ms·

> Remember, in may 1996, the very first HTTP protocol version (HTTP/1.0) was born. Uh, what? HTTP predates 1996. The first version was HTTP/0.9, from 1991. 0.9

> Remember, in may 1996, the very first HTTP protocol version (HTTP/1.0) was born. Uh, what? HTTP predates 1996. The first version was HTTP/0.9, from 1991. 0.9 is still supported by a lot of web servers, too!

hdhzy 10y ago
And browsers! Causing interesting bugs: https://bugs.chromium.org/p/chromium/issues/detail?id=669800 https://bugs.chromium.org/p/chromium/issues/detail?id=669800
- kupiakos 10y ago
  Wow, that's a disaster. Hopefully it was a wake-up call to the Shoutcast administrators to not depend on 10+ year old software that doesn't follow actual standards.
  - kuschku 10y ago
    You mean, you expect tenthousands of broadcasters, with millions of users, to switch their systems over, because some people at Google decided that they should control the web? It's very questionable that such a move can even be made without a discussion in one of the web standards groups, and can be made entirely by Google employees. In the long term, changing this is unavoidable, but without warning, and without discussion, deprecating a widely used standard is not exactly awesome. You'd expect such a change to require discussion in standards groups, months of warnings before it happens, etc
    - Chronos 10y ago
      Anyone who depends on the Internet for their business should know better than to run 10 year old unpatched Internet server software.
      - kuschku 10y ago
        You mean, a 10 year old, unpatched protocol. You don't know the actual software running behind it, and how they might have modified it. And just deprecating an entire category of protocols still in use without Google even sending an email as warning to the servers that still use it, well, that’s insane.
yes_or_gnome 10y ago
Personally, I've found it hard to find much information about pre-HTTP/1.0. To my understanding, "HTTP/0.9" is a retroactive version number. The original HTTP protocol was incredibly simple. An HTTP Request was simply "GET /", then the response was just the content immediately followed by a closed connection. There were no headers. "HTTP/0.9" is used to describe the implementations of "HTTP/1.0" before it was -- for lack of a better word -- 'ratified'. If you, or anyone, has more information or analysis of pre-HTTP/1.0 protocol implementations (client or server), I would be very interested in reading it. Also, if there is a public, pre-HTTP/1.0 HTTP server available on the internet, I would very much like to check it out. Thanks. Edit: Alternatively, if it's possible to run an pre-HTTP/1.0 server (or client), that would be phenomenal. It only occurred to me after making the comment, however I highly doubt that it would be a simple process to get one running. I suspect that I wouldn't be able to spin a Docker container with some ancient version of Apache (I assume due to changes in the Linux environment, shared libraries, changes to gcc, etc.), but possibly, a VM running an equally-ancient version of Red Hat (pre-EL) would do the trick.
- TazeTSchnitzel 10y ago
  This is the only reference I've known: https://www.w3.org/Protocols/HTTP/AsImplemented.html https://www.w3.org/Protocols/HTTP/AsImplemented.html It's a little more sophisticated than GET /, as you can also specify a full URL. > Also, if there is a public, pre-HTTP/1.0 HTTP server available on the internet Most HTTP/1.0+ web servers still support HTTP/0.9. I don't know of any 0.9-only servers though, but there's probably some.

hdhzy 10y ago

And browsers! Causing interesting bugs: https://bugs.chromium.org/p/chromium/issues/detail?id=669800 https://bugs.chromium.org/p/chromium/issues/detail?id=669800

kupiakos 10y ago
Wow, that's a disaster. Hopefully it was a wake-up call to the Shoutcast administrators to not depend on 10+ year old software that doesn't follow actual standards.
- kuschku 10y ago
  You mean, you expect tenthousands of broadcasters, with millions of users, to switch their systems over, because some people at Google decided that they should control the web? It's very questionable that such a move can even be made without a discussion in one of the web standards groups, and can be made entirely by Google employees. In the long term, changing this is unavoidable, but without warning, and without discussion, deprecating a widely used standard is not exactly awesome. You'd expect such a change to require discussion in standards groups, months of warnings before it happens, etc
  - Chronos 10y ago
    Anyone who depends on the Internet for their business should know better than to run 10 year old unpatched Internet server software.
    - kuschku 10y ago
      You mean, a 10 year old, unpatched protocol. You don't know the actual software running behind it, and how they might have modified it. And just deprecating an entire category of protocols still in use without Google even sending an email as warning to the servers that still use it, well, that’s insane.

yes_or_gnome 10y ago

Personally, I've found it hard to find much information about pre-HTTP/1.0. To my understanding, "HTTP/0.9" is a retroactive version number. The original HTTP protocol was incredibly simple. An HTTP Request was simply "GET /", then the response was just the content immediately followed by a closed connection. There were no headers. "HTTP/0.9" is used to describe the implementations of "HTTP/1.0" before it was -- for lack of a better word -- 'ratified'. If you, or anyone, has more information or analysis of pre-HTTP/1.0 protocol implementations (client or server), I would be very interested in reading it. Also, if there is a public, pre-HTTP/1.0 HTTP server available on the internet, I would very much like to check it out. Thanks. Edit: Alternatively, if it's possible to run an pre-HTTP/1.0 server (or client), that would be phenomenal. It only occurred to me after making the comment, however I highly doubt that it would be a simple process to get one running. I suspect that I wouldn't be able to spin a Docker container with some ancient version of Apache (I assume due to changes in the Linux environment, shared libraries, changes to gcc, etc.), but possibly, a VM running an equally-ancient version of Red Hat (pre-EL) would do the trick.

TazeTSchnitzel 10y ago
This is the only reference I've known: https://www.w3.org/Protocols/HTTP/AsImplemented.html https://www.w3.org/Protocols/HTTP/AsImplemented.html It's a little more sophisticated than GET /, as you can also specify a full URL. > Also, if there is a public, pre-HTTP/1.0 HTTP server available on the internet Most HTTP/1.0+ web servers still support HTTP/0.9. I don't know of any 0.9-only servers though, but there's probably some.