On Mon, May 02, 2022 at 03:22:43PM -0700, Chime Hart wrote: > Hi All: 1 of my google news-alerts pointed me to an article which first gave > me a 403 error, but even after ajusting an option for user agent, still says > "cannot connect" This does work in elinks, also LINKS, and w3m. However, > what else I am not understanding. In w3m there are maybe 171 lines on 1 > page, while both other browsers have at least 2 pages. I have my screen set > at 180lines by 270 columns. Here is an url > https://globalriskinsights.com/2022/05/the-russo-ukrainian-war-and-nagorno-karabakhs-faltering-ceasefire/ > I would rather access this in L Y N X as I better understand how to save > files. I also want to run this story through rdrview. I've also just tried > the main site, same result. Thanks so much in advance. > Chime
There are two problems: a) the 403 is returned because of Lynx's user-agent string. b) suppressing the user-agent string, gnutls (or lynx) returns an error HTTP: Hit unexpected network read error; aborting connection; status 0:The TLS connection was non-properly terminated.. That might be some particular detail of the algorithms used. It could be a bug in lynx -- or like the user-agent... Lynx's trace says Secure 256-bit TLS1.3 (ECDHE_RSA_AES_256_GCM_SHA384) HTTP connection links and Elinks' "=" screen show similar results - but not identical: SSL Cipher: TLS1.3 - ECDHE-RSA - AES-256-GCM - AEAD - X.509 (compr: NULL) For instance, that AEAD might be relevant. w3m's "=" screen shows a lot about the signature, but no summary like those. (by the way, links (not elinks) also says it's using brotli compression, but -- I added that in lynx recently -- doesn't affect the result). -- Thomas E. Dickey <dic...@invisible-island.net> https://invisible-island.net ftp://ftp.invisible-island.net
signature.asc
Description: PGP signature