Thanks, I got it working. My goal was to avoid repeating both the proxy
config and the password blocks, but I was able to make them inlcudes to
avoid a bunch of duplicate lines.
Thanks again!
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,254625,254652#msg-254652
_
ok, so i opened the log using glogg and have pasted a relevant sequence into
pastebin here:
http://pastebin.com/wTQs6ALb
any tips welcome, thanks
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,254523,254651#msg-254651
___
nginx mailing list
Sorry, I got a little ahead of myself.
If I only want to display all files named
"the_nginx_mailing_list_guys_are_genuises*" - can I do that?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,254649,254650#msg-254650
___
nginx mailing list
ngin
Is there a way to have autoindex only display certain files?
If I only want to display a file named
"the_nginx_mailing_list_guys_are_genuises*" - can I do that?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,254649,254649#msg-254649
___
ngin
oh, so the log file is 3.5GB in size and even though the server has enough
RAM to handle it, the log viewer crashes and gedit gets stuck too.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,254523,254648#msg-254648
___
nginx mailing list
nginx
On Thu, Nov 06, 2014 at 05:35:09PM -0500, nrahl wrote:
Hi there,
> The expected response is a password prompt on all locations, unless the IP
> matches, in which case allow, or the path starts with /Public, in which case
> allow.
nginx config is based on "one request is handled in one location";
> You have denied access by ip address here, so 403 is the expected
> response, no?
>
>
> You may have more success if you can describe what response you
> expect,
> and provide a complete (small) server{} configuration that
> demonstrates
> the unwanted behaviour that you see.
>
The expected r
On Thu, Nov 06, 2014 at 04:47:28PM -0500, nrahl wrote:
Hi there,
> With debug logging on, I ahve confirmed it is matching the correct location.
Do you also see the subrequest that accesses a different location that
has its own configration?
> With:
>
> location ^~ /Public {
> satisfy any
> Are you sure that the test url that you are requesting matches this
> location?
>
> There may be more useful information in the debug log regarding what
> is going wrong for you.
>
With debug logging on, I ahve confirmed it is matching the correct location.
With:
location ^~ /Public {
On Thu, Nov 06, 2014 at 09:51:12AM -0500, nrahl wrote:
Hi there,
> I've also tried:
>
> location /Public { auth_basic off; allow all; }
>
> But adding "allow all" causes the password prompt to appear on that location
> again.
location ^~ /public {
auth_basic off;
allow all;
}
seems
ping ?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,254535,254639#msg-254639
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
> location /Public { auth_basic off; }
>
This prevents the password prompt from appearing on /Public, but results in
an immediate 403 Forbidden error on that location.
I've also tried:
location /Public { auth_basic off; allow all; }
But adding "allow all" causes the password prompt to appear o
Hello!
On Thu, Nov 06, 2014 at 12:32:58AM -0500, khav wrote:
> I am seeing a lot of these entries in my logs
>
> Nov 6 04:29:13 sv1 kernel: nginx[62598]: segfault at 0 ip 00438f38
> sp 0 0007fffa5a934c0 error 4 in nginx (deleted)[40+e2000]
> Nov 6 04:29:13 sv1 abrt[22289]
13 matches
Mail list logo
