403 forbidden with lynx www browser

[B.R.]

*There is none so deaf than those who will not hear.* :o|
​Well​ if you two understand each other, find where nginx handles some
user-agents differently than others. I am sure the developers would be more
than glad to learn about it. Everyone is, actually.
---
*B. R.*

On Tue, Nov 24, 2015 at 12:00 AM, Sylvain BERTRAND <
sylvain.bertrand at gmail.com> wrote:

> On Mon, Nov 23, 2015 at 07:31:15PM +0000, Nelson, Erik - 2 wrote:
> > B.R. Monday, November 23, 2015 2:26 PM
> > On Mon, Nov 23, 2015 at 12:23 AM, Sylvain BERTRAND <
> sylvain.bertrand at gmail.com> wrote:
> > >>That's why I'm posting here: *Only nginx* www sites does block lynx.
> Something
> > >>is not right there: a default aggressive blocking policy from nginx?
> >
> > >​There is a difference between 'only websites I visit which happen to
> > >use nginx' and 'every nginx websites'
> >
> > That may be true, but it's missing the point.  This has come up before
> on the
> > ML.  The point is that he has observed something systemic.  Maybe it's a
> > default configuration that's tighter (as he suggested), maybe it's that
> > admins who use nginx just hate lynx, or maybe it's something else.
> >
> > Whatever it is, there's *something* about nginx that's different.
>
> You got it right.
>
> The last web site... a friend sent me the link (:p), had to remove the
> user-agent from http headers.
>
> http://www.rawstory.com/2015/11/hacker-collective-anonymous-claims-isis-has-plans-for-more-attacks-on-sunday/
>
> --
> Sylvain
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20151124/25273304/attachment.html>