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_read_timeout 600s;
proxy_send_timeout 600s;
proxy_connect_timeout 20s;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection upgrade;
proxy_set_header Host $host;
}

Best regards,
Vintila Mihai Alexandru

On 7/2/2016 7:21 PM, Ben wrote:
> Hi,
>
> I have a PBX that has a webRTC feature (i.e. you login to PBX website
> and you have a virtual handset with all the features).
>
> Is it feasible or possible to use NGINX as a reverse proxy to handle
> webRTC ?
>
> A basic NGINX config just using proxy_pass doesn't seem to work, so
> I'm guessing there's probably more to it than that ?
>
> THanks !
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx