|
FoxWeb MessageThe FoxWeb Service has returned the following message:Could Not Connect to FoxWeb Broker. Broker has probably not been started. |
However, the HTTP status code returned was 200, indicating a successful page. This makes detecting problems in our monitoring software more challenging. It would be far more appropriate if foxweb.exe returned a 500-level error, indicating a server error.
Now I could do a page-scrape for the word "error" or something, but that's not a good approach, as my own code often prints what it calls "errors" in user input, or a user might even use the word "error" in a dynamic page title.
Even worse, it doesn't catch the problem that I'm actually trying to detect at the moment:
FoxWeb Message The FoxWeb Service has returned the following message: Could not Create Socket |
The word "error" never appears on that page. I haven't been able to capture the status code from this page yet (our socket problem is sparodic), but I'm guessing it will be 200, given that the other error page I cited returns a 200.
Can you tell me what status code the "Could not create socket" page returns?
I really can't wait for an update to foxweb.exe on this problem, so I'll be screen-scraping this one for "Could not Create Socket". I encourage you to put it on the short list for the next release, or even an interim patch. I'm guessing it would be pretty simple to implement.
-dave
ps. Let me reiterate: Our socket problem is not caused by FoxWeb in any way. Don't mistake this message as a complaint about FoxWeb's socket usage...FoxWeb is fine. FoxWeb is the victim of some other errant situation on our server.
--
David Hempy
Internet Database Administrator
Kentucky Educational Television
(859)258-7164 - (800)333-9764