peili

@aburnson Thank you for suggesting to use urlRewriter. Using the URL rewriter function I can reverse proxy that traffic. However the signalling url is dynamic (based on load and location)....

In case anybody needs a reference for nginx/openresty. ``` location / { proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Host $host; resolver 8.8.8.8 [::1]; resolver_timeout 10s; if ($arg_redirect) { set_by_lua $urldecoded 'return ngx.unescape_uri(ngx.arg[1])'...

@yaghmaie I am busy right now, but I hope in the next days I can provide some more details on our configuration. @aburnson We had multiple enterprise organization reporting the...

@yaghmaie What's are the error messages you're seeing in the Chrome console? I think you just want to replace the hostname for the singaling url using regex /\.*signal.*?aws/gi ` configuration.urls.urlRewriter...

Great to hear. I also recommend requiring that the domain matches those of signaling URLs (ending in app.chime.aws) to prevent the service from proxying arbitrary WebSocket traffic.

+1

Any process on this issue so far?

Do you know when Google/Mozilla are going to support this feature? I couldn't find clear informations on the roadmaps..

Any updates on "attaching remote audio/video stream"? Audio seems to work. Video not?

After some more testing, I can share using ```smoothWheelZoom: 'center',``` doesn't reproduce the issue.