Issue with HTTPS response returning 505 HTTP Version Not Supported

WaitronCharm via Lynx-dev <[email protected]> Mon, 24 Aug 2026 19:51:25 +0000

Newsgroups	gmane.comp.web.lynx.devel
Message-ID	<iOCYndF4_14ut2jZO3cBOrP9Ls780KLsg-RzI4aeXVG6yUFz2gMV6fzOmcmzECIEfQ3L_4WxJX0-ACDh_wQzdCaiSO6nwSOebg2zFVBwA5k=@proton.me>

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>

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.

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.