Closed GoogleCodeExporter closed 9 years ago
I realized i didn't use the very last version of mod_pywebsocket because i
downloaded directly instead of using svn.
using ssn, to get the last version of the files, i reinstalled mod_pywebsocket.
I have no longer the mod_python error but instead a 400 bad request response
from the server for every page i try to load.
Complete error is the following
**************
Bad Request
Your browser sent a request that this server could not understand.
***********
But On the other hand, websockets seem to work now. I tried
var ws= new WebSocket("ws://localhost/echo");
and
ws.send('click') and the response was true for the last command.
So now I just have to understand why server respond with an error for every
other request
Someone to help me ? I would really like to make this work
Thanks
Original comment by christop...@gmail.com
on 20 Oct 2011 at 3:51
It seems to be the ame issue as
https://groups.google.com/forum/#!topic/pywebsocket/1tjOny5I3Pw
Old implementation always fallback to apache when pywebsocket could not handle
client request correctly.
But, the newest spec requires 400 bad request for wrong opening handshake.
My recent change to support 400 broke compatibility around it.
I submit new change to fix this issue.
Now, pywebsocket checks handler existence then sends http response with 400.
If handler doesn't exist, pywebsocket will fallback to apache as you expect.
Could you try r583?
Original comment by toyoshim@chromium.org
on 21 Oct 2011 at 8:56
Works like a charm, thank you very much.
I can play with websockets now
Original comment by christop...@gmail.com
on 21 Oct 2011 at 9:20
Original comment by toyoshim@chromium.org
on 25 Oct 2011 at 6:00
Original issue reported on code.google.com by
christop...@gmail.com
on 20 Oct 2011 at 2:50