creativcoder / pywebsocket

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

echo_wsh.py is not working #80

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. After I install pywebsocket and run the standalone.py
2. Then I try out the demo in example folder.
3. I used javascript api to call ws://myurl/websocket_handlers/echo
4. I got it connect to the websocket server for a few second, then disconnect.
5. I got onError message that return undefine. Then it closes the connection.

What is the expected output? What do you see instead?
The expect output, I want to see your demo working so I can send and receive 
message without closing the port automatically.

What version of the product are you using? On what operating system?
I use ubuntu server with apache2.2

Please provide any additional information below.
http://www.khmer.org/websock_handlers/

Original issue reported on code.google.com by thaigirl...@gmail.com on 2 Dec 2010 at 9:01

GoogleCodeExporter commented 9 years ago

Original comment by tyoshino@chromium.org on 9 Dec 2010 at 9:56

GoogleCodeExporter commented 9 years ago
I'll do further investigation, but for now, please check out reqtimeout.conf 
and reqtimeout.load in your Apache2 configuration directory. Ubuntu (Apache 
2.2.15) has them and they are setting so short timeout for request reading. By 
removing ReadRequestTimeout, the socket won't be closed so immediately though 
there's still some other timeout limits e.g. keepalive.

Original comment by tyoshino@chromium.org on 9 Dec 2010 at 10:21

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.Run the "example" app in the codebase
2.
3.

What is the expected output? What do you see instead?
1. There shouldn't be any warning in the terminal. But I am getting the below:
[micadeyeye@micadeyeye src]$ python mod_pywebsocket/standalone.py -p 8088 -d 
example
[2012-09-10 21:02:01,731] [WARNING] __main__.WebSocketRequestHandler: 
localhost.localdomain - code 404, message File not found
[2012-09-10 21:02:04,021] [WARNING] __main__.WebSocketRequestHandler: 
localhost.localdomain - code 404, message File not found
[2012-09-10 21:02:12,372] [WARNING] __main__.WebSocketRequestHandler: 
localhost.localdomain - code 404, message File not found
[2012-09-10 21:02:12,413] [WARNING] __main__.WebSocketRequestHandler: 
localhost.localdomain - code 404, message File not found
[2012-09-10 21:03:19,797] [WARNING] __main__.WebSocketRequestHandler: 
localhost.localdomain - code 404, message File not found

2. Both FF and Chrome didn't catch the WS response; yet the webpage showed that 
the same message that was sent was received.

What version of the product are you using? On what operating system?
Most recent. I did an svn as instructed

Please provide any additional information below.
None

Original comment by micadey...@gmail.com on 10 Sep 2012 at 7:20

GoogleCodeExporter commented 9 years ago
re 1: Please ignore those warnings. They're printed when the server couldn't 
find the requested resource as well as error log of Apache.

re 2: What do you mean by "the WS response"?

Also could you please paste the output of console.html?

Original comment by tyoshino@chromium.org on 11 Sep 2012 at 3:33

GoogleCodeExporter commented 9 years ago
FYI, this warning commonly happens when favicon.ico is requested.

Original comment by tyoshino@chromium.org on 25 Jan 2013 at 8:09

GoogleCodeExporter commented 9 years ago
Closing old bugs. Please reopen if this is still valid.

Original comment by tyoshino@chromium.org on 23 Apr 2014 at 10:49