[
https://issues.apache.org/jira/browse/WAVE-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ali Lown updated WAVE-320:
--------------------------
Comment: was deleted
(was: It sounds a lot like they 'automated configuration script' is doing
something awkward to your network configuration settings. That 403 looks
ominous as to where it is sending the traffic.
If you could find out exactly what this script is changing, it would help here
in debugging why your specific case isn't working.
Why are you still using company settings where you are not at work?
The reason GWave can get through is because it uses an XHR-Polling method when
behind firewalls (which send the data over the same port and in the same format
as standard internet traffic), but WIAB defaults to WebSockets which are much
more picky about the network setup to ensure the socket does open to the server
without interference.
I am looking into a 'fallback' method for WIAB using XHR (socket.io seems to
support this) since I also have a place where I can't get WebSockets due to a
draconian network policy.)
> 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
