Hello,
Is there a variable which stores the IP address of the proxy if I use the
real-ip module.
E.g. to log the client-ip as well as the proxy-ip (the IP address of the
physical connection).
Thanks a lot!
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,253024,253024#msg-253024
This patch adds two features:
mp4_limit_rate 1.1; # multiplied by average bitrage
mp4_limit_rate_after 15s; # time
http://doppelbauer.name/nginx-1.6.1-mp4_limit_rate.patch
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,252946,252946#msg-252946
_
Hello,
My NGINX got a denial of service. The machine proxied large files using
"proxy_store".
Someone was creating an artifical request for a rarely used file, causing
NGINX to download a big file from upstream, then he immediately closed the
connection. NGINX continued to download this file.
Then
Hello,
Is there a good way to disable "proxy_store", if the parameter "start=" is
set?
The down below configuration works, but I get an error message:
"[crit] ... open() "/dev/null.04" failed (13: Permission denied)
while reading upstream ..."
Using "set $proxy_store off;" won't work, bec
Hmm, this patch is still not in nginx-1.3.16.
It would be great to have this feature in vanilla nginx.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,234926,238461#msg-238461
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mai
> Weibin: Have you thought of upstreaming the no_buffer patch to nginx
1.3.x
> so it could become part of next nginx stable version 1.4 ?
> It'd be really nice to have the no_buffer functionality in stock nginx!
I agree. Nginx is such an excellent product - but this is a missing
feature.
Thanks
M
> I keep getting the "upstream sent invalid header while reading response
header from upstream"
> error when using the no_buffer patch..
The patch does not work for you?
Thanks
Markus
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,234926,237090#msg-237090
_
Are there any plans to integrate this feature into NGINX?
It would be very great.
> Maxim Dounin:
> As a non-default mode of operation the aproach taken is likely
> good enough (not looked into details), but the patch won't work
> with current nginx versions - at least it needs (likely major)
>
> Pasi Kärkkäinen
> People want nginx to *not* save the http PUT/POST request to disk
> when using nginx as a reverse proxy.
Have the same problem. I use "haproxy" in front of "nginx" - but this
more a bad hack than a workaround.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,234926,2
> I know nginx team are working on it. You can wait for it.
Hopefully they will find a solution!
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,234926,236723#msg-236723
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/
Machine ""front-end"":
haproxy (port 80) -> proxies to "port 8080" and "machine upload"
nginx (port 8080)
Machine "upload":
nginx (port 80) via "front-end"
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,236568,236699#msg-236699
___
nginx mai
haproxy does not buffer the request - it proxies immediately.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,236568,236668#msg-236668
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Example:
Size of POST-request: 10 GB (e.g. HD video)
Upload-time: 4h
The front-server proxies the request to the upload-server.
After the upload has finished, the uploading client wants a quick "all
fine"-message (maximum 30 seconds).
If the upload-server gets the stream directly, the machine has
This would be an excellent feature!
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,234926,236640#msg-236640
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Thanks a lot!
> Also it'd be very nice to get this feature to standard nginx,
> many people need it!
100% true.
I hate this workaround via "haproxy"
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,236568,236576#msg-236576
___
nginx mailing l
Hello,
Large POST-request are buffered to disk, before passed to the backend.
The backend has troubles to parse the POST-data, if the requests are huge
(some GB).
We use "haproxy" in front of "nginx", to workaround this issue.
But this causes extra load on the server.
Is there a chance to disable
16 matches
Mail list logo