It works with something like this:
location ^~ /webrtc/ {
if ($my_https = "off") {
return 301 https://$host$request_uri;
}
limit_conn conn 100;
limit_req zone=basic burst=3000 nodelay;
proxy_pass http://backend;
proxy_set_header X-Real-IP $remote_addr;
proxy_r
Have you also checked that the DNS returns the correct value? As the
valid option means that nginx will ask the DNS server again, but if the
DNS replies with same old ip.. Also you might check using directly the
hostname as it might be possible that there is a bug when using variables.
Best re
From Manual:
By default, nginx caches answers using the TTL value of a response. An
optional|valid|parameter allows overriding it:
resolver 127.0.0.1 [::1]:5353 valid=30s;
Before version 1.1.9, tuning of caching time was not possible, and
nginx always cached answers for the duration
Try it with:
sendfileon;
tcp_nodelayon;
tcp_nopush off;
Best regards,
Mihai Vintila
On 4/22/2015 8:42 AM, GuiPoM wrote:
Short update, as I am still struggling with this problem: Same issue for
HTTP, if I route an external port to nginx on my raspberry. But if I route
