Hello!
On Wed, Nov 12, 2014 at 3:01 PM, josephlim wrote:
> I was wondering what happens when multiple workers access the
> ngx.shared.dict in the http lua module ? Are there conflicts/locking that
> could potentially impact performance of nginx? We are talking about 32
> workers in my use case.
>
Hi guys,
I was wondering what happens when multiple workers access the
ngx.shared.dict in the http lua module ? Are there conflicts/locking that
could potentially impact performance of nginx? We are talking about 32
workers in my use case.
Thank you in advance
Posted at Nginx Forum:
http://foru
On Tue, Nov 11, 2014 at 04:42:56PM +, Tinte garcia, Miguel Angel wrote:
Hi there,
> http {
>
>upstream load_balancer {
>server localhost:8080/Instance1;
>server localhost:8080/Instance2;
>server localhost:8080/Instance3;
>}
On Wed, Nov 12, 2014 at 03:38:03AM -0500, sudarshan wrote:
Hi there,
> If query parameters in the request looks like this
>
> /something.cgi?param_name=1¶m-name=2
>
> I can access 'param_name' as $arg_param_name. How do I access 'param-name'
> though? $arg_param-name will not work since as far
Hi,
With the help of HttpLuaModule I'm trying to duplicate every request
into two upstreams. Here is my configuration:
site.conf
---
upstream prod_upstream {
server 127.0.0.1:5000;
server 127.0.0.1:5001;
}
upstream dev_upstream {
server 127.0.0.1:6000;
}
server {
Hello!
On Wed, Nov 12, 2014 at 05:26:27AM -0500, carlg wrote:
> HI,
>
> I want to configure our nginx to be a little more paranoid concerning file
> access.
>
> Right now, i am using rules like :
>
> location /includes {
> allow 127.0.0.1;
> deny all;
> }
>
> ... but i need to repeat this kin
The solution is to access it using lua as ngx.var[ "arg_param-name" ].
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,254782,254786#msg-254786
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
HI,
I want to configure our nginx to be a little more paranoid concerning file
access.
Right now, i am using rules like :
location /includes {
allow 127.0.0.1;
deny all;
}
... but i need to repeat this kind of rules for every folders, and then
restrict access to the php files inside. So our rul
If query parameters in the request looks like this
/something.cgi?param_name=1¶m-name=2
I can access 'param_name' as $arg_param_name. How do I access 'param-name'
though? $arg_param-name will not work since as far as nginx is concerned the
variable name ends at $arg_param. Is there a workaround f
Hi,
> I would like nginx to manage the requests among the three instances above,
depending on the load. Is it correctly defined?
what you have defined is a round-robin-based loadbalancing,
what you probably would like to do is a loadbalancing based on the
connections processed:
http://nginx.or
10 matches
Mail list logo
