Browser Support on Windows 7

[sikosis]

Hi,

I know Dashing doesn't work in IE, because it doesn't support server side sent events.

In saying that, Dashing doesn't work for Chrome or Firefox on Windows 7.

So, I'm wondering, what else, ie. what other technologies Dashing requires.

A colleague wrote a Webkit based (WebKitBrowser.dll) project using Visual Studio and Dashing does NOT work in it.

However, when running this W3C Server-Sent Events test:-

http://www.w3schools.com/html/html5_serversentevents.asp

that works. So, there must be something else that dashing requires on Windows.

Cheers

Phil

[Norvares]

Hi,

it seems like the bug happens between dashing+thin and Windws 7 Browsers. I hosted the dahing test board on a fresh ubuntu server, tried to connect from Firefox/Chrome and it doesn't work either.
It seems like thin doesn't delivers the event-stream for Windows Browser if you don't kill the server.

Please try to install another webserver like puma or webrick and use it instead of thin:

rackup -p 80 -s webrick

or

rackup -p 80 -s puma

Cheers

Steffen

[jcamelon]

This is not just a windows 7 browser issue. I was seeing the same thing on OS X 10.8.5 w/ Chrome 31, FF 25 & Safari 6.1

[TimSmith714]

I switched to using puma and it started working immediately
I did change the port to 3030 so it worked with the same link as previous attempts

[stuartstevenson]

using webrick as recommended by @Norvares worked for us

[netsloh]

Hi,
I had animation problems on iOS and using puma did the trick.
I'm now trying to start dashing on startup using puma but that just won't work.
When I start puma with --deamon option the dashing jobs don't work anymore.
Any suggestions or startup scripts? Thanks in advance!
btw: I'm running raspbian

[JC1738]

i experienced this same problem using a docker image and the default dashing project. Using rackup -p 3030 -s webrick fixed the issue.

[kaburkett]

I was experiencing issues I perceived to be windows based. I have Ubuntu installed on Windows 10 via default Windows features... I was able to see apache over port 80 fine, but every time I tried to connect on any port configured with thin via ruby on my ubuntu instance- the windows browser would time out (firefox, chrome, ie, didnt matter). I tried so many troubleshooting methods...

I found this thread and decided to give webrick a shot instead of thin and it's working like a charm now.

Thanks all