xhr possible errors?

85 views
Skip to first unread message

theyak

unread,
Oct 5, 2012, 5:25:14 PM10/5/12
to soc...@googlegroups.com
I get a bunch of things that look like this:

POST /chat/946/1t_efayn/xhr 0ms 200
POST /chat/370/0d0g5ghg/xhr 0ms 200
POST /chat/099/b1p8g1mv/xhr 0ms 200
POST /chat/635/c4gjctpx/xhr 0ms 200
POST /chat/452/myzihuqx/xhr 0ms 200
POST /chat/946/1t_efayn/xhr 0ms (unfinished)
POST /chat/452/myzihuqx/xhr 0ms (unfinished)
POST /chat/370/0d0g5ghg/xhr 0ms (unfinished)
POST /chat/635/c4gjctpx/xhr 0ms (unfinished)
POST /chat/099/b1p8g1mv/xhr 0ms (unfinished)

Any idea what they are? Are they bad? Does this mean users are not connecting?

Marek Majkowski

unread,
Oct 5, 2012, 6:28:44 PM10/5/12
to yakk...@gmail.com, soc...@googlegroups.com
Hi!

You seem to be using sockjs-node. Thanks for writing to this mailing list!

Have you considered reviewing the readme?

It's available here: https://github.com/sockjs/sockjs-node

Here's the relevant option if you don't like to see those messages:

> log (function(severity, message))
> It's quite useful, especially for debugging, to see some messages printed by a SockJS-node library. This is done using this `log` function, which is by default set to `console.log`. If this behaviour annoys you for some reason, override `log` setting with a custom handler. The following `severities` are used: `debug` (miscellaneous logs), `info` (requests logs), `error` (serious errors, consider filing an issue).
It means that Sockjs-node is spamming your console. It's neither good
or bad. It depends what you want to do.

Cheers!
Marek

theyak

unread,
Oct 5, 2012, 7:33:28 PM10/5/12
to soc...@googlegroups.com, yakk...@gmail.com
Yup, I read the readme. These just looked like error conditions, but I guess it's OK.
Reply all
Reply to author
Forward
0 new messages