[
https://issues.apache.org/jira/browse/WAVE-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13446367#comment-13446367
]
Ali Lown commented on WAVE-366:
-------------------------------
Yes, __websocket_address is being correctly set to the same as
http_frontend_public_address and http_frontend_addresses variables when I set
http_websocket_public_address as such.
Notably, in the event that all 3 are 'localhost:9898' then websockets over SSL
works.
If I set them to '192.168.1.128:9898' (my local machine address) then the
websockets works + breaks (depending on how you access).
Looking at it in the chrome developer tools, the request seems to be pointing
to the correct place (in this instance: 'wss://192.168.1.128:9898/socket', but
it doesn't get a response as if it isn't listening there...
Steps to reproduce: (Ensure you always use a 'clean' browser setup (even Chrome
Incognito Mode seems to keep something between tabs in the same window))
1) Setup server with all 3 config variables (http_frontend_public_address,
http_frontend_addresses, http_websocket_public_address) to 'localhost:9898'
2) Visit in a 'clean' browser as 'localhost:9898' -> This _always_ works
correctly
3) Setup server with all 3 config variables as '192.168.1.128:9898' (or
whatever your local (assuming NAT'd) address is)
4) Ensure in hosts file machine-name points to 192.168.1.128 (or whatever you
setup)
4) Visit in a 'clean' browser as 'machine-name:9898' -> observe it fails to
connect to websockets
5) Visit in a 'clean' browser as '192.168.1.128:9898' -> observe it connects to
websockets
6) In the same session as 5) , now connect to 'machine-name:9898' -> observe it
now connects to websockets
So, if you visit as IP, then use the name websockets connects (caching
somewhere?)
If you try to visit directly as name, then it _always_ fails to connect to
websockets (in a 'clean' session).
This is how I can reproduce this at least.
@Yurize: localhost always works fine for SSL testing, hence @Vjrj, this appears
to work ok during your testing (do you only use localhost?)
Then again, maybe this is a chrome bug. For reference I can reproduce this
using Chromium 22.0.1229.2 (150678) on 2 different machines.
> Websockets fail to connect to server with SSL enabled
> -----------------------------------------------------
>
> Key: WAVE-366
> URL: https://issues.apache.org/jira/browse/WAVE-366
> Project: Wave
> Issue Type: Bug
> Components: Server
> Reporter: Ali Lown
> Assignee: Ali Lown
> Labels: ssl, websocket
>
> I think it is a result of review #5375 for WAVE-357.
> Disabling SSL allows the websocket to connect to the configured port without
> issue.
> When SSL is enabled, although wss is correctly used, the socket is unable to
> be established.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
