[
https://issues.apache.org/jira/browse/WAVE-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503885#comment-14503885
]
Ali Lown commented on WAVE-120:
-------------------------------
Assuming Chrome has fixed this bug by now, then this RPC and assosciated logic
can be removed from ServerRpcProvider.
> Workaround for websocket cookie bug
> -----------------------------------
>
> Key: WAVE-120
> URL: https://issues.apache.org/jira/browse/WAVE-120
> Project: Wave
> Issue Type: Bug
> Components: Server
> Priority: Trivial
> Labels: StarterProject
>
> There is currently a bug in the websocket implementation in Chrome whereby
> the browser doesn't send HTTP cookies to the websocket server.
> We've implemented a workaround for this bug in this CL:
> http://codereview.waveprotocol.org/224001/
> ... which adds a way for the client to manually send its session cookie to
> the server through an RPC.
> Confirmed on:
> Chrome for Linux, 7.0.517.41 beta
> ---
> Issue imported from
> http://code.google.com/p/wave-protocol/issues/detail?id=119
> Label: Type-Defect
> Label: Priority-Low
> Label: Maintainability
> Stars: 1
> State: open
> Status: Accepted
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
