Hi.
I found the mistake. The Firewall-Policy was configured but the used
Host-Object was wrong. There were the wrong ip addresses for my webservrs
added. I changed this and can reach my webservers now.
Thanks for your help.
Mit freundlichen Grüßen
Jörg Kastning
IT-Systemadministrator
SYNAXON
I've written an additional feature into the Auth Request module (from
http://mdounin.ru/hg/ngx_http_auth_request_module/) that allows a user to
control the behaviour of the auth_request in such a way that it can act as a
FastCGI authorizer. This patch that I have written allows the user to
specify
Maxim Dounin Wrote:
---
> What you are trying to do should be possible with
> NGX_HTTP_SUBREQUEST_IN_MEMORY - this way subrequest body will be
> available in memory instead of being sent to a client. But it's
> not currently supported for fa
Hello!
On Sat, Apr 20, 2013 at 01:18:40AM +0200, Roberto Moreda wrote:
> Is someone working in OCSP validation of client certificates?
> I just want to know if someone is interested or working already
> before trying to do it myself :-)
AFAIK, nobody is working on it. Code in OCSP Stapling sup
Steve, you are a Linux genius, and I am but a humble plebe, forever in
your debt.
On Sun, Apr 21, 2013 at 1:09 PM, Steve Holdoway wrote:
> At a guess, /var or /var/www isn't readable by www-data
>
> Steve
>
> On 22/04/2013, at 7:50 AM, "Paul N. Pace" wrote:
>
>> I have set up a server on Rackspa
At a guess, /var or /var/www isn't readable by www-data
Steve
On 22/04/2013, at 7:50 AM, "Paul N. Pace" wrote:
> I have set up a server on Rackspace using Ubuntu 12.04 and the nginx stable
> PPA.
>
> Using the default root location of /usr/share/nginx/html the
> index.html file is displayed w
I have set up a server on Rackspace using Ubuntu 12.04 and the nginx stable PPA.
Using the default root location of /usr/share/nginx/html the
index.html file is displayed when I call the public IP address of the
server.
If I change the root location to my own /var/www/example.com/public
the index
i know that 1.3.x is development version, but is it stable enough to be used
in production? as stated here:
http://forum.nginx.org/read.php?2,221377,221390#msg-221390
Tell me if i figured that right : if the 1.2.x is based on 1.2.0 - then its
basic functionality is about 1 year old, and the main c
can you make sure that anyway.com ist reachable?
sounds like the path to your front-lb is somehow
not working.
i think i dont need to ask for an nginx-restart after config-changes?
if you upstream-config is messy or your upstream-servers
are unreachable you should usually see a:
502 Bad Gatew
