Custom Query (2297 matches)

Хотелось бы предложить добавить гибкости в модули ограничения соединений/запросов, а именно комбинированный ключ, так, как это сейчас возможно в ключе для зоны кеширования.

Т.е. что-то наподобие limit_zone test "$binary_remote_addr|$server_name" 10m;

RPM package on site has bad signature - it is not possible to install it:

# uname -a
Linux XXXXXXXX.panline.net 2.6.18-274.7.1.el5 #1 SMP Thu Oct 20 16:21:01 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux

# rpm -qpli nginx-1.0.13-1.el5.ngx.x86_64.rpm
error: nginx-1.0.13-1.el5.ngx.x86_64.rpm: Header V4 RSA/SHA1 signature: BAD, key ID 7bd9bf62

# rpm -Uvh nginx-1.0.13-1.el5.ngx.x86_64.rpm
error: nginx-1.0.13-1.el5.ngx.x86_64.rpm: Header V4 RSA/SHA1 signature: BAD, key ID 7bd9bf62
error: nginx-1.0.13-1.el5.ngx.x86_64.rpm cannot be installed

​The documentation says:

add_header Adds headers to the HTTP response when the response code is equal to 200, 204, 301, 302 or 304.

I'm trying to add Access-Control-Allow-Origin (and related) headers for cross-domain purposes, and I'm unable to use add_header to add it to 201 responses, which is making cross-domain resource-creation awkward.

I'd like it if add_header could be modified to support at least 201 responses, and preferably any success response (i.e. 2xx)