Custom Query (2311 matches)

Hi.

I've tested on 1.22.1 and 1.24.0 versions and on both client_body_buffer_size is ignored within location context while client_max_body_size works correctly.

location /images/upload {
	try_files $uri $uri/ /index.php?$args;

	client_body_buffer_size 32M;
	client_max_body_size 64M;
}

If I set it outside in server context it works but that's not a valid solution for me.

client_body_buffer_size 32M;
location /images/upload {
	try_files $uri $uri/ /index.php?$args;

	client_max_body_size 64M;
}

Hello,

I'm experiencing weird issue involving nginx variables, rewrite module and the location directive from the http_core module. I'm trying to use variable's value as a rewrite URI. The thing is when I use query parameters in the variable value nginx location directive is trying to access the file with the query arguments included.

For example, I'm having the following configuration in my server context.

set $test /test.php?test=1;
rewrite ^/my/test$ $test last;

When trying to access the /my/test location I get the following error message:

GET /my/test HTTP/2.0" 404
open() "/app/public_html/test.php?test=1" failed (2: No such file or directory)

When not using variable for the replacement uri everything works fine:

rewrite ^/my/test$ /test.php?test=1 last;
GET /my/test HTTP/2.0" 200

Is this intentional behaviour due to how nginx is compiling the rewrite directives at configuration stage, or I've stumbled upon some bug?

Nginx sends proxy protocol header without triling "\r\n" when unix socket path is too long, Sample config: ` strema {

server {

listen *.80;

proxy_pass unix:/var/run/1.socket; proxy_protocol on;

}

server {

listen unix:/var/run/1.socket prtoxy_protocol; proxy_pass 127.0.0.1:8080; proxy_protocol on;

}

} `

When send simple HTTP GET request to :80 - it;s ok;

But when socket oath is ontr, than 80 chars - nginx sends data like this ( WITHOUT "\r\n" separator after proxy protocol header ): ` PROXY TCP 1.2.3.4 unix:.... pott1 port2GET `