Bug #3168
openserver push timeout
0%
Description
My server-push-timeout is set to 600. But I see messages every 5 minutes. Is this a bug?
[2014-May-19 13:52:24.526976] 25652 - [info] "WebRequest: took 0.272ms" 10.160.24.27 - - [2014-May-19 13:57:24.531509] "POST /?wtd=xwJfz8oWFsAdIhMz HTTP/1.1" 200 51
[2014-May-19 13:57:24.531546] 25652 - [info] "WebRequest: took 0.336ms" 10.160.24.27 - - [2014-May-19 14:02:24.536956] "POST /?wtd=xwJfz8oWFsAdIhMz HTTP/1.1" 200 51
[2014-May-19 14:02:24.536991] 25652 - [info] "WebRequest: took 0.295ms" 10.160.24.27 - - [2014-May-19 14:07:24.541849] "POST /?wtd=xwJfz8oWFsAdIhMz HTTP/1.1" 200 51
I also have web-sockets set to true and my browser (Chrome Version 34.0.1847.137 m) supports web-sockets. Is there a way to tell if the server is in fact using web-sockets. I actually did not expect to see the server-push messages with web-sockets turned on.
Wt version is 3.3.2 and I'm using the wthttpd connector.
Thanks
suresh
KD Updated by Koen Deforche over 12 years ago
Hey,
The 5minutes is derived from session.timeout (10 minutes by default, divided by 2).
You do not actually seem to have enabled server push (from this log), i.e. using WApplication::enableUpdates()
It indeed appears that either web sockets isn't configured properly or isn't working. With web sockets you will not see "POST" messages, instead there will be a single 101 response. Can you verify that Wt is reading your configuration file (it gives the location of the file that it is reading on startup). It may also be that even though browser and server both support WebSockets, an intermediate proxy isn't.
Regards,
koen
KD Updated by Koen Deforche over 12 years ago
- Status changed from New to Feedback
- Assignee set to Koen Deforche