yrift / jwebsocket

Automatically exported from code.google.com/p/jwebsocket
0 stars 0 forks source link

1.0b4 Demos don't work when server is local machine and chat demo is run from filesystem #147

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Download jWebSocket-1.0-nb11201.zip, install the server and client
2. run the chat demo
3.

What is the expected output? What do you see instead?

I expect the chat client to connect to the server.  I get an immediate 
disconnect and the following error message on the server:

2011-12-16 14:55:14,021 DEBUG - TCPEngine$EngineListener: Client trying to 
connect on port #61819...
2011-12-16 14:55:14,023 DEBUG - TCPEngine: Parsing handshake request: GET 
/jWebSocket/jWebSocket HTTP/1.1\nUpgrade:websocket\nConnection: Upgrade\nHost: 
127.0.0.1:8787\nOrigin: null\nSec-WebSocket-Protocol: 
org.jwebsocket.json\nSec-WebSocket-Key: 
Buh9fET6J3TNQ+HqmDfVKA==\nSec-WebSocket-Version: 13\n\n
2011-12-16 14:55:14,024 ERROR - EngineUtils: Client origin 'null' does not 
match allowed domains.

What version of the product are you using? On what operating system?

OS is 64 bit Windows 7, home premium edition.

version is from   jWebSocket-1.0-nb11201.zip

Please provide any additional information below.

With Chrome 14, I was successfully using 1.0b1 of jWebSockets.  When Chrome 
forced its update to 16 (which changed the websocket version supported) I 
installed the new jWebSocket, which gave me the null NS problem. 

Original issue reported on code.google.com by flying...@gmail.com on 16 Dec 2011 at 8:06

GoogleCodeExporter commented 9 years ago
It's not a problem of demos, it seems to be an issue from the server, I've get 
same error with other websocket clients.

Original comment by hernan.e...@gmail.com on 23 Dec 2011 at 3:31

GoogleCodeExporter commented 9 years ago
When testing with the demo chat.html the same problem occurs.
Windows 7 64bit, Safari 5.1.2, jWebSocket-1.0-nb11201

2011-12-30 00:11:29,746 DEBUG - TCPEngine$EngineListener: Client trying to 
connect on port #3063...
2011-12-30 00:11:29,746 DEBUG - TCPEngine: Parsing handshake request: GET / 
HTTP/1.1\nUpgrade: WebSocket\nConnection: Up
grade\nHost: localhost:8787\nOrigin: file://\nSec-WebSocket-Protocol: 
org.jwebsocket.json\nSec-WebSocket-Key1: 2U    34
=C9,U4004   88~\nSec-WebSocket-Key2: = M 2 47  K6 Z 3J860 50  I\n\n¼Z8¦¼7±z
2011-12-30 00:11:29,747 ERROR - EngineUtils: Client origin 'file://' does not 
match allowed domains.

Original comment by Philipp....@gmail.com on 29 Dec 2011 at 11:14

GoogleCodeExporter commented 9 years ago
A temporary solution is to add <domain>null</domain> or 
<domain>file://</domain> into jWebSocket.xml at the tcp configuration et netty 
configuration.

I don't know what happens exactly but it was working when I tried with 2 or 3 
example demo.

I hope it will be fixe soon.
Best regards.

Original comment by vianney....@gmail.com on 30 Dec 2011 at 2:24

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
I also have a problem in trying Chat and Shared Canvas in the following site :
http://jwebsocket.org
http://enapso.org/demos/chat

Can anyone tell me what the exactly happen ?
Best regards.

Original comment by ariefis...@gmail.com on 25 Jan 2013 at 9:45

GoogleCodeExporter commented 9 years ago
it doesn't work with adding <domain>null</domain> or <domain>file://</domain> 
into jWebSocket.xml at the tcp configuration!!!!!
what is " et netty configuration " ???
It's a shame that even the demo doesn't work!
If this is published because one person tried this on 2-3 file, it's another 
shame!
Get serious! There's a lot of people interested in this and what a first step 
disappointment!

Original comment by j...@koroglu.net on 28 Feb 2013 at 12:13

GoogleCodeExporter commented 9 years ago
Did this issue ever get fixed? Do I need to try and find another web socket 
package?
Running:
64 bit Windows 7, home premium edition.
jWebSocket-1.0-nb20507.zip

Original comment by daisy...@gmail.com on 22 Apr 2013 at 7:40