Hi!
> > > proxy_next_upstream error timeout invalid_header http_500 http_502
> > > http_503 http_504 http_404;
>
> What you describe looks very familiar - there was such a bug which
> manifested itself with backup servers and proxy_next_upstream
> http_404. It was fixed in 1.3.0/1.2.1 though:
>
I am trying to read if a specific value is set (passed) as a POST using
request_body.
What I am trying to do is:
server {
..
if ($request_body ~ "API-value-Iwanttocheck") {
set $my_api "TRUE";
}
And later on pass to the backend server:
location / {
proxy_pass http://backend:80;
Hello!
On Sat, May 11, 2013 at 04:13:38PM +1000, Daniel Black wrote:
[...]
> > A request for /img/file_doesnt_exist.jpg results in the backend server
> > (192.168.129.90) getting continuous requests for the same file (which
> > doesn't exist there either so 404 each time), while the original
> >
It's looking like he permissions issue may be related to chroot (OpenBSD
appears to run nginx in 'jail').
This all seems sane - but unfortunately, my *nix-foo isn't strong enough to
work out which is the best path for my socket (file) to live.
Can anyone help me with this?
Thanks!
G
___
On 11 May2013, at 07:52 , B.R. wrote:
> Hello,
>
> Is Wheezy supported for Nginx?
Not yet. I plan to build packages for wheezy and ubuntu 13.04 in a
week or two.
>
> Would it be possible to use role-based package selection for the Nginx APT
> source?
No, I see potential problems here: ngi
Hi,
According to http://nginx.org/r/access_log, the access_log directive
cannot be used within an `if` in `server`, only within an `if` in
`location`.
Indeed, it doesn't actually work within an `if` directly within
`server`, but variables can be used to seemingly achieve identical
result.
Thanks. I've been coming to that conclusion myself.
Take care,
Dan
At 7:00 PM +0400 5/11/13, Maxim Dounin wrote:
Hello!
On Fri, May 10, 2013 at 02:35:35PM -0400, Daniel Griscom wrote:
That's great information, but now I need to figure out how to
selectively proxy to my websocket backend w
Hello!
On Fri, May 10, 2013 at 02:35:35PM -0400, Daniel Griscom wrote:
> That's great information, but now I need to figure out how to
> selectively proxy to my websocket backend when $http_upgrade is
> "websocket". I see the following choices:
>
> 1) Have nginx listen at port 80, and proxy all
Hello!
On Fri, May 10, 2013 at 11:13:42AM +0800, Stefan Xenon wrote:
> Hi!
> I want to use nginx as a caching proxy in front of an OCSP responder.
> The OCSP requests are transmitted via HTTP POST.
>
> Hence, I configured nginx as follows:
>
> proxy_cache_path /tmp/nginx/cache levels=1:2 keys_
