[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Lynx-dev] [PATCH] Re: Cannot use duckduckgo suddenly

From: Axel Beckert
Subject: [Lynx-dev] [PATCH] Re: Cannot use duckduckgo suddenly
Date: Thu, 17 Dec 2015 02:44:22 +0100
User-agent: Mutt/1.5.21 (2010-09-15)

Hi again,

On Thu, Dec 17, 2015 at 02:29:29AM +0100, Axel Beckert wrote:
> > 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.

Attached a quick and dirty proof of concept patch against the current
lynx-cur package in Debian Unstable. With that applied, I can use
DuckDuckGo again. (Well, didn't try HTTPS and POST, but the search
form shows up again.)

                Kind regards, Axel
/~\  Plain Text Ribbon Campaign                   | Axel Beckert
\ /  Say No to HTML in E-Mail and News            | address@hidden  (Mail)
 X   See | address@hidden (Mail+Jabber)
/ \  I love long mails: | (Web)

Attachment: HTTP_1.1.diff
Description: Text Data

reply via email to

[Prev in Thread] Current Thread [Next in Thread]