You don't seem to have a index file in web root___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Thu, Nov 26, 2015 at 12:17:23PM +1100, Sylvain BERTRAND wrote:
> On Wed, Nov 25, 2015 at 07:29:53PM +0100, Lukas Tribus wrote:
> > https://support.cloudflare.com/hc/en-us/articles/200169226-Why-am-I-getting-a-403-error-
> >
> >
> > That is however not the case with rawstory.com.
> >
> >
> >
On Wed, Nov 25, 2015 at 07:29:53PM +0100, Lukas Tribus wrote:
> https://support.cloudflare.com/hc/en-us/articles/200169226-Why-am-I-getting-a-403-error-
>
>
> That is however not the case with rawstory.com.
>
>
> Therefor:
> - rawstory.com uses cloudflare, but
> - cloudflare does not block lynx
> The server header gives more information but what's displayed in the xhtml
> body
> of the 403 response is "nginx" only which is what will be displayed in the
> user
> www browser, and that's mis-leading and unfair for nginx. Maybe somebody
> should contact CloudFlare to make them modify their
On Wed, Nov 25, 2015 at 12:43 AM, Sylvain BERTRAND <
sylvain.bertr...@gmail.com> wrote:
> Maybe somebody
>
> should contact CloudFlare to make them modify their response bodies from
> stock
> nginx.
>
Do you qualify as somebody? :o)
---
*B. R.*
_
On Tue, Nov 24, 2015 at 06:41:39PM +0100, B.R. wrote:
> On Tue, Nov 24, 2015 at 2:07 PM, Sylvain BERTRAND <
> sylvain.bertr...@gmail.com> wrote:
>
> > Then, if I understand well, it's a CloudFlare mistake, who happens to use
> > nginx only.
> >
> > That makes sense, and is quite unfair for nginx t
On Tue, Nov 24, 2015 at 2:07 PM, Sylvain BERTRAND <
sylvain.bertr...@gmail.com> wrote:
> Then, if I understand well, it's a CloudFlare mistake, who happens to use
> nginx only.
>
> That makes sense, and is quite unfair for nginx to be displayed while
> applying
> CloudFlare blocking.
>
> That's re
On Tue, Nov 24, 2015 at 03:57:21PM +0300, Maxim Dounin wrote:
> Hello!
>
> On Tue, Nov 24, 2015 at 10:00:01AM +1100, Sylvain BERTRAND wrote:
>
> > On Mon, Nov 23, 2015 at 07:31:15PM +, Nelson, Erik - 2 wrote:
> > > B.R. Monday, November 23, 2015 2:26 PM
> > > On Mon, Nov 23, 2015 at 12:23 AM,
Hello!
On Tue, Nov 24, 2015 at 10:00:01AM +1100, Sylvain BERTRAND wrote:
> On Mon, Nov 23, 2015 at 07:31:15PM +, Nelson, Erik - 2 wrote:
> > B.R. Monday, November 23, 2015 2:26 PM
> > On Mon, Nov 23, 2015 at 12:23 AM, Sylvain BERTRAND
> > wrote:
> > >>That's why I'm posting here: *Only ngin
*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
On Mon, Nov 23, 2015 at 07:31:15PM +, Nelson, Erik - 2 wrote:
> B.R. Monday, November 23, 2015 2:26 PM
> On Mon, Nov 23, 2015 at 12:23 AM, Sylvain BERTRAND
> wrote:
> >>That's why I'm posting here: *Only nginx* www sites does block lynx.
> >>Something
> >>is not right there: a default aggres
You missed the parts where Francis and I suggested about testing against
nginx.org and/or nginx.com websites.
Is those reply correctly, the nginx product is definitely not the source of
the trouble.
I could also provide you with domains I serve with nginx, which do not use
any sort of user-agent fi
On Mon, Nov 23, 2015 at 10:23:20AM +1100, Sylvain BERTRAND wrote:
> On Sun, Nov 22, 2015 at 05:25:11PM +, Francis Daly wrote:
Hi there,
> > Probably they have configured their servers to deny any request that
> > includes "libwww" in the User-Agent.
>
> I'm about to block sending the user ag
B.R. Monday, November 23, 2015 2:26 PM
On Mon, Nov 23, 2015 at 12:23 AM, Sylvain BERTRAND
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
Hello,
On Mon, Nov 23, 2015 at 12:23 AM, Sylvain BERTRAND <
sylvain.bertr...@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 websit
On Sun, Nov 22, 2015 at 05:25:11PM +, Francis Daly wrote:
> On Sun, Nov 22, 2015 at 03:05:25PM +1100, Sylvain BERTRAND wrote:
> > On many nginx powered web sites, I must not send the user agent or I'll get
> > a
> > 403 forbidden.
>
> The administrators of those web sites do not want you as a
On Sun, Nov 22, 2015 at 03:05:25PM +1100, Sylvain BERTRAND wrote:
Hi there,
> On many nginx powered web sites, I must not send the user agent or I'll get a
> 403 forbidden.
The administrators of those web sites do not want you as a customer.
Probably they have configured their servers to deny a
It's important that the right access is set for the files and folders in
/var/www/testdomain.ovh/web.
Nginx is running as user www-data (per default) and folders needs to be set
with (at least) execute and read permissions for www-data. For files read
permission is the least required.
~sjums
On
On Sat, Mar 07, 2015 at 01:01:11PM +0100, JACK LINKERS wrote:
Hi there,
> Hi I can't access my domain after installing nginx and coinfigurong the
> default server conf file :
What request do you make; what response do you get; what response do
you want; and what do the logs say?
f
--
F
Well, I feel pretty stupid now. I used an automatic script to generate that
config and I just assumed that the rewrite would be included.
Thanks & Oops.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,239004,239011#msg-239011
___
nginx maili
Why would Nginx automatically redirect mydomain.com do mydomain.com/w/ if
you don't tell it to do so?
Your error log shows that you are trying to list the files of your root
directory (so it means you don't have an index file to be served there),
which is forbidden by default Nginx configuration t
21 matches
Mail list logo
