[
https://issues.apache.org/jira/browse/WAVE-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13254212#comment-13254212
]
Ali Lown commented on WAVE-320:
-------------------------------
It was my understanding that the problem was normally due to the network setup,
with the use of IIS7 in proxy mode causing the issues in most network setups
since IIS7 doesn't understand the websocket handshake so simply drops the
traffic instead.
The only workaround from a client perspective is to use Firefox (pre 10/11 when
native websocket support was added) to force the server to fall back to XHR
instead.
As for WIAB server admins -> either switch on SSL, or force XHR always.
> Wave does not work on Google Chrome browser
> -------------------------------------------
>
> Key: WAVE-320
> URL: https://issues.apache.org/jira/browse/WAVE-320
> Project: Wave
> Issue Type: Bug
> Components: Web Client
> Affects Versions: 0.1
> Environment: Windows 7 Professional 64-bit with SP1
> Google Chrome 16.0.912.75 m (release)
> Reporter: Özgür KINACI
> Labels: chrome, windows
>
> When I log in to http://waveinabox.net/, it shows status as "Offline" and I
> receive error message:
> "A turbulence detected! Please save your last changes to somewhere and reload
> the wave."
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
