Hello,
> > How to proxy request to different upstream by url request parameters?
> http://nginx.org/en/docs/http/ngx_http_upstream_module.html#sticky
this is part of the commercial subscription, but you can probably obtain
the same using a MAP like that:
map $arg_key $backend {
key1 bac
Hello,
> How to proxy request to different upstream by url request parameters?
http://nginx.org/en/docs/http/ngx_http_upstream_module.html#sticky
Cheers,
Thomas
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/n
upstream upstream1{
}
upstream upstream2{
}
upstream upstream3{
}
upstream upstream4{
}
request url is http://.com/id=xxx&key=xxx
if (id is 1~100 key=key1) send to upstream1
if (id is 1~100 key=key2) send to upstream2
if (id is 101~200 key=key1) send to upstream3
if (id is 101~200 key=
On Sat, Mar 22, 2014 at 11:37:38AM +1300, Steve Holdoway wrote:
Hi there,
> Sadly not one mention of the correct way to handle %1 and $1 in either
> of these pages.
Can you describe in words what you want your nginx config to do?
As in: this request leads to that response.
I can try guessing a
Hello. I'm running nginx as a proxy for back-end servers that are
returning a non-standard HTTP status phrase. I'd like to be able to
rewrite the status to something standard. For
example, if the back-end returns:
HTTP/1.1 400 Not Understood
I'd like to rewrite to:
HTTP/1.1 400 Bad Request
T
Sadly not one mention of the correct way to handle %1 and $1 in either
of these pages.
Anyone??
Cheers,
steve
On Thu, 2014-03-20 at 22:14 -0700, Payam Chychi wrote:
> Hi Steve,
>
> that's a lot of apache nonsense ;) that you shouldn't need
>
> check out:
> http://nginx.org/en/docs/http/conve
To anyone using (or considering) the nginx-sflow-module for monitoring,
then please use version 0.9.9 or later. Previous versions generated
incorrect sFlow output in deployments with multiple worker-processes.
Symptoms included spurious spikes in Ganglia graphs.
https://code.google.com/p/nginx-
Nginx binds file extensions with file types:
http://nginx.org/en/docs/http/ngx_http_core_module.html#types
An examples there links to
http://nginx.org/en/docs/http/ngx_http_core_module.html#default_type
---
*B. R.*
___
nginx mailing list
nginx@nginx.org
h
How to configure that?
the files xxx-yyy-ddd-hhh and xxx-yyy-ddd-hhh.html have the same html code
in it.
Typing example.com/xxx-yyy-ddd-hhh.html in the browser is OK.
Typing example.com/xxx-yyy-ddd-hhh in the browser get the wronge
content-type application/octet-stream.
A text/html content-typ
Hello!
On Fri, Mar 21, 2014 at 11:22:42AM +0530, Geo P.C. wrote:
> We have a setup in which nginx proxypass is working fine for tomcat like
> this:
>
> server {
> listen 80;
> server_name app.geo.com;
> location /app {
> proxy_pass https://192.168.1.100:8080/app;
> }
>
> Now while accessi
10 matches
Mail list logo