Re: [Lynx-dev] Any idea what one can do about the people who feel the need to block lynx
On 2020-06-22 23:30, Claudio Calvelli wrote: > Any suggestion on what one can tell these ignorants so they may > learn something? I know that the OWASP "Core Rule Set (CRS)" (prior to version 3.0) for the Apache "mod_security" module had blocking based on the User-Agent header that included lynx and curl (at least until a more recent release) https://en.wikipedia.org/wiki/ModSecurity#Former_Lynx_browser_blocking so if admins are just downloading a "yep, sounds like a good default list to me" configuration without actually checking what it blocks, lynx users can end up with "406 Not Acceptable" errors. If you encounter those and tweaking your settings so that lynx sends the user-agent with "l_y_n_x" instead of "lynx" and that solves it, you might have better luck asking the admin to upgrade to CRS3 which solves the issue. That said, because you're getting a 403 rather than a 406, it sounds like that might not be the case here. -tim ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
Re: [Lynx-dev] Any idea what one can do about the people who feel the need to block lynx
Sounds like you got a boiler plate response. It's unfortunate, but I find a lot of supposed tech support requests these days run up against a brick wall as regards actual help. You're almost always quoted a nonrelevant piece of gibberish that has no bearing on the problem you're trying to solve. The only thing to do is continue explaining (nicely if possible, though sometimes, it gets to the point where you just gotta vent on them), and eventually, someone will realize what you're asking isn't covered by their generic template responses, and you'll get an actual response that addresses the issue. How many iterations this takes varies greatly, and in one case, after over a month of back and forths on a nearly daily basis, I finally gave up, and vowed never to use that site ever again, which interestingly enough I actually broke earlier today, and tried to purchase something else from them, which met with the same exact issues I'd gone back and forth with them about nearly 5 years ago. Good to know some things never change. On 6/22/2020 5:30 PM, Claudio Calvelli wrote: As we all know, there are ignorants who imagine that they need to block lynx from accessing their sites. I just contacted one with evidence that they block based on user-agent and asked why they feel the need to deny access - and what do they come up with? Please switch off your VPN or proxy then click here: https://ceoemail.com I wasn't using a VPN or proxy, and of course that is completely irrelevant to their User-Agent filtering. (and of course the URL they quoted resulted in a "403 forbidden" because they have no idea what they are doing) Any suggestion on what one can tell these ignorants so they may learn something? Claudio Calvelli ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
Re: [Lynx-dev] Any idea what one can do about the people who feel the need to block lynx
Hi Claudio: Just an opinion, but I think an Internet culture has gone far past our favorite friendly browsers. Yes its rather inconvenient when traveling to one of these sites with a 403 error, then having to go in an options menu and uncheck the user agent box, before submitting. Sure thats anoying, but these sites where you just get a blank page such as that of my Cable TV company at spectrum.net Or these sites like radiodiscussions.com which employ DOS cloud protection. Obviously there are millions of sites which either require javascript or make it hard to use without it. Its been many years since I was able to talk a webmaster in to restoring a printer friendly page at the BBC for one. Now, as so many of these web site owners are so hungup on javascript, their minds are made up. But almost as bad, its much more of a challenge to write, as "whois" will not show an exact contact. Obviously I wish you luck, but short of an FCC or Supreme Court intervention, we may be out of luck Chime ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
[Lynx-dev] Any idea what one can do about the people who feel the need to block lynx
As we all know, there are ignorants who imagine that they need to block lynx from accessing their sites. I just contacted one with evidence that they block based on user-agent and asked why they feel the need to deny access - and what do they come up with? Please switch off your VPN or proxy then click here: https://ceoemail.com I wasn't using a VPN or proxy, and of course that is completely irrelevant to their User-Agent filtering. (and of course the URL they quoted resulted in a "403 forbidden" because they have no idea what they are doing) Any suggestion on what one can tell these ignorants so they may learn something? Claudio Calvelli ___ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
