On Thu, Dec 17, 2015 at 02:29:29AM +0100, Axel Beckert wrote: > Hi, > > On Wed, Dec 16, 2015 at 07:15:35PM -0600, Tim Chase wrote: > > > On 2015-12-16 23:39, Ian Collier wrote: > > > > doing it by hand works too: > > > > > > > > $ (echo "GET / HTTP/1.1" ; echo "host: duckduckgo.com" ; echo ) > > > > | nc duckduckgo.com 80 > test.html > > > > > > But if you send HTTP/1.0 instead of 1.1 it closes the connection > > > without sending any data. > > > > Just received confirmation from the DuckDuckGo folks that they > > dropped HTTP/1.0 support: > > > > https://twitter.com/duckduckgo/status/677291463957422080 > > > > But really, HTTP/1.1 (AKA RFC-2068) became official in January of > > 1997, replacing the HTTP/1.0 standard (RFC-1945) that had only become > > the standard ~2 years prior. According to [1], lynx supported > > HTTP/1.1 as of version 2.5 but according to [2] it wasn't supported > > as of 2005. So nearly 20 years later, one might hope that lynx > > supported 1.1. :-( > > Lynx already sends the Host header which is required for HTTP/1.1 (and > became a defacto must for HTTP/1.0 when virtual hosting came up like > 15 years ago). > > So the only thing missing to support a minimal HTTP/1.1 would be to > send a (hardcoded) "Connection: close" header to avoid running into a > persistent connection. AFAIK that should already suffice to get back > into the game.
It's been a while since I looked at the differences, but I recall it as more than just that. At the moment I was working to flush out the backlog... -- Thomas E. Dickey <dic...@invisible-island.net> http://invisible-island.net ftp://invisible-island.net
signature.asc
Description: Digital signature
_______________________________________________ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
