Forum: NGINX Nginx Websocket proxy with Microsoft IE 10 client

Eb571ecf764ed5778e59f342e9186cd3?d=identicon&s=25 Alder Network (Guest)
on 2013-11-21 00:17
(Received via mailing list)
Is that a known issue? Any remedy available?
Thanks,

- Alder
A8108a0961c6087c43cda32c8616dcba?d=identicon&s=25 Maxim Dounin (Guest)
on 2013-11-21 09:49
(Received via mailing list)
Hello!

On Wed, Nov 20, 2013 at 03:17:11PM -0800, Alder Network wrote:

> Is that a known issue? Any remedy available?

What's the issue?

--
Maxim Dounin
http://nginx.org/en/donation.html
Eb571ecf764ed5778e59f342e9186cd3?d=identicon&s=25 Alder Network (Guest)
on 2013-11-21 23:13
(Received via mailing list)
when client is Internet Explorer 10, the websocket session didn't get
proxy'd to websocket server (websocketpp)  other browser
clients work fine.
A8108a0961c6087c43cda32c8616dcba?d=identicon&s=25 Maxim Dounin (Guest)
on 2013-11-22 13:53
(Received via mailing list)
Hello!

On Thu, Nov 21, 2013 at 02:12:47PM -0800, Alder Network wrote:

> when client is Internet Explorer 10, the websocket session didn't get
> proxy'd to websocket server (websocketpp)  other browser
> clients work fine.

Works fine here, just tested:

192.168.56.1 - - [22/Nov/2013:16:48:39 +0400] "GET /websocket.html
HTTP/1.1" 304 0 "-" "Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1;
Trident/6.0)"
192.168.56.1 - - [22/Nov/2013:16:49:03 +0400] "GET /websocket/ HTTP/1.1"
101 21 "-" "Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1;
Trident/6.0)"

(Note "101" response logged after a tab is closed.)

You may want to find out more details, see
http://wiki.nginx.org/Debugging for some hints.

--
Maxim Dounin
http://nginx.org/en/donation.html
Please log in before posting. Registration is free and takes only a minute.
Existing account

NEW: Do you have a Google/GoogleMail, Yahoo or Facebook account? No registration required!
Log in with Google account | Log in with Yahoo account | Log in with Facebook account
No account? Register here.