Error with WebSockets and UTF-8 encodings about play-with-docker

[xetorthio]

Related to this is that maybe we should switch to socket.io. It has lots of
fallbacks and seems to sve all these crazy issues.

On Mon, Oct 10, 2016, 20:04 Marcos Nils [email protected] wrote:

If within an instance you write curl www.google.com you'll see that the
javascript console shows: WebSocket connection to 'ws://
play-with-docker.com/sessions/952dc23e-c830-40e2-ba0d-35ec548d0127/instances/goofy_keller/attach'
failed: Could not decode a text frame as UTF-8. and terminal stops
working

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#10, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAIhp72_I5K_GyfY0tT1Pd3AlylIwzx1ks5qysRkgaJpZM4KTE9T
.

[akalipetis]

I think we could go with Socket.io - @alexellis also had an issue connecting to WebSockets over a proxy. I might jump into this sometime during the week 🎉

[marcosnils]

@akalipetis might help us with this :)

[marcosnils]

@akalipetis @xetorthio found and fixed the problem :D

[akalipetis]

🎆🎇✨🎉

That needed a huge amount of code 😂

On Wed, Oct 19, 2016, 06:39 Marcos Nils [email protected] wrote:

@akalipetis https://github.com/akalipetis @xetorthio
https://github.com/xetorthio found the problem :D

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#10 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAwHopNPRPID_2zBM8LebvlOyjd_Kdcbks5q1ZDmgaJpZM4KTE9T
.