Re: Issue with HTTPS response returning 505 HTTP Version Not Supported

Thomas Dickey <[email protected]> Mon, 24 Aug 2026 19:10:11 -0400

Newsgroups	gmane.comp.web.lynx.devel
Message-ID	<[email protected]>

On Mon, Aug 24, 2026 at 07:51:25PM +0000, WaitronCharm via Lynx-dev wrote:
> Dear Lynx Developers,
> 
> I recently encountered an issue when attempting to fetch the source of https://www.berlin.de using Lynx:
> 
> $ lynx -source https://www.berlin.de
> <html><head><title>505 HTTP Version Not Supported</title></head><body><h1>505 HTTP Version Not Supported</h1><p>This server only supports HTTP/1.1 or higher.</p></body></html>

in lynx.cfg:

.h1 Internal Behavior
.h2 HTTP_PROTOCOL
# Normally Lynx negotiates HTTP/1.0, because it does not support chunked
# transfer (a requirement for all HTTP/1.1 clients), although it supports
# several other features of HTTP/1.1.  You may encounter a server which does
# not support HTTP/1.0 which can be used by switching to the later protocol.
#HTTP_PROTOCOL:1.0
 
> It appears that the server is rejecting the request because it does not
> support HTTP/1.0, only HTTP/1.1 or higher.  I wanted to check if there are
> any existing options or flags within Lynx that can force the client to use
> HTTP/1.1 when making requests or if there are plans to support this
> explicitly in future releases.

yes, the server is defective, but there's a lot of that going around
 
> Additionally, I am curious about the broader trend -- are there known shifts or retirement plans for HTTP/1.0 support in servers? Is this a common occurrence that we should be aware of when developing or maintaining tools like Lynx?
> 
> Thanks in advance for any insights or guidance.
> 
> 

-- 
Thomas E. Dickey <[email protected]>
https://invisible-island.net

signature.asc (application/pgp-signature, 659 B)