Re: [Lynx-dev] site newly returns 503 unavailable for lynx [PS]

[Tim Chase]

whoops, that might have been mod_security, not mod_proxy.  Same
concern still holds though, a poorly configured server.

-tim

On 2021-08-23 13:23, Tim Chase wrote:
> On 2021-08-23 13:18, Karen Lewellen wrote:
> > Have you tried that link this morning?  
> 
> There does seem to be some sort of sniffing going on at the server.
> I tried it in a handful of browsers (lynx, links, links2, w3m,
> dillo, chromium, firefox).  Some of them consistently gave a 503
> error, some consistently loaded.
> 
> I've seen some sites like this before where some aspect (user-agent,
> IPv4-vs-IPv6, etc) causes it to fail in one browser while working
> fine in another.  Sadly, it seems to be somewhat intentional (there
> was a particular Apache module, mod_proxy, that was known for
> blocking certain user-agents and causing other interruptions in the
> name of "security")
> 
> So I wish I could give some magic "oh, just do this", but the
> website is adversarially (mis)configured.
> 
> -tim
> 
> 
> 
>