|
From: | Martin Pala |
Subject: | Re: Websockets monitoring |
Date: | Wed, 5 Mar 2014 12:34:18 +0100 |
Thanks for the trace. It seems that your server responds with pong (in packet no. 11), but before that, it sends chat text frame with "who" prompt (in packet no. 9): No. Time Source Destination Protocol Length Info 4 0.000384 127.0.0.1 127.0.0.1 HTTP 309 GET / HTTP/1.1 No. Time Source Destination Protocol Length Info 6 0.001237 127.0.0.1 127.0.0.1 HTTP 197 HTTP/1.1 101 Switching Protocols No. Time Source Destination Protocol Length Info 8 0.001303 127.0.0.1 127.0.0.1 WebSocket 70 WebSocket Ping [FIN] WebSocket 1... .... = Fin: True .000 .... = Reserved: 0x00 .... 1001 = Opcode: Ping (9) 0... .... = Mask: False .000 0000 = Payload length: 0 No. Time Source Destination Protocol Length Info 9 0.002225 127.0.0.1 127.0.0.1 WebSocket 75 WebSocket Text [FIN] WebSocket 1... .... = Fin: True .000 .... = Reserved: 0x00 .... 0001 = Opcode: Text (1) 0... .... = Mask: False .000 0101 = Payload length: 5 Payload Text: "who" No. Time Source Destination Protocol Length Info 11 0.003986 127.0.0.1 127.0.0.1 WebSocket 70 WebSocket Pong [FIN] WebSocket 1... .... = Fin: True .000 .... = Reserved: 0x00 .... 1010 = Opcode: Pong (10) 0... .... = Mask: False .000 0000 = Payload length: 0 At this point Monit expects response to its own request, so the protocol test failed. The server response is OK, we just need to allow server messages (such as this prompt) not related to our own ping request. The websocket.org's service works differently ... it's not chat service, just echo, so it doesn't send any prompt. Will fix the test. Can i use your websocket servis (from the previous email) to verify the test works with it? Regards, Martin On 05 Mar 2014, at 12:13, Mehul Ved <address@hidden> wrote: Hi Martin, |
[Prev in Thread] | Current Thread | [Next in Thread] |