This is a problem on the webserver. What happens is that the "client" (SA in this case) sends a request (URL request) and the server sends an answer in HTTP/1.1
Within this answer the the servers says how much bytes it will send back within the "body" of the HTTP packet. And the server doesn't send the correct number of bytes (most of the time it sends LESS bytes then it says in the header). From an RFC point of view that is a problem and therefore we see this as being a problem (on the server). Most browser don't care a lot about the RFC and accept about everything. Servers Alive tries to follow the RFC as much as possible. Dirk Bulinckx. From: Servers Alive Discussion List [mailto:sal...@woodstone.nu] On Behalf Of Kobi Shalom Sent: Friday, March 06, 2009 12:51 PM To: Servers Alive Discussion List Subject: [SA-list] Hello, We recive a lot of socket alerts: "The current socket connectionhas been reset. (200-OK)" This error occur on up to 7 web sites that look fine from browser view, We try to catch problem on server side both on system and application, but all look fine, We monitoring this web site 2 minutes cycle and recive daily hundred alerts Any idea? ____________________________ Regards, Kobi Shalom KOH IT Solutions ____________________________ Office : 09-7451893 Fax : 057-7974765 Mobile : 052-3546396 Mail : mailto:k...@koh.co.il (mailto:k...@koh.co.il) Web : www.koh.co.il (http://www.koh.co.il/) Your Data Is Our Concept! To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list.
