It looks like a simple User-Agent redirection they have implemented lynx -head https://www.washingtonpost.com/opinions/
gives me a 301 response to the home page but lynx -head -useragent=Mozilla https://www.washingtonpost.com/opinions/ gives a 200 response and the requested page loads You can just set the U-A header to something they haven't blocked in lynx options. --- Stefan Caunter Hamilton http://smashgods.ca/ On Sun, Jan 21, 2018 at 11:14 AM, <[email protected]> wrote: > > Beginning 19 January lynx can't browse any subdirectory of > http://www.washingtonpost.com/. If I try to browse > https://www.washingtonpost.com/opinions/ , for example, lynx switches > automatically to its home page. > > Jan 21 08:53:46 mydomain lynx[1270]: > http://www.WashingtonPost.com/opinions > Jan 21 08:53:49 mydomain lynx[1270]: http://www.washingtonpost.com/ > Jan 21 08:53:52 mydomain lynx[1270]: https://www.washingtonpost.com/ > Jan 21 08:53:59 mydomain lynx[1270]: > https://www.washingtonpost.com/opinions/ > Jan 21 08:54:03 mydomain lynx[1270]: https://www.washingtonpost.com/ > > links works, though it reports an invalid certificate first. > > russell bell > > _______________________________________________ > Lynx-dev mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/lynx-dev _______________________________________________ Lynx-dev mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lynx-dev
