|
hmmm talking about BAD english....
When you do a webrequest you get back a header part and a
page part. For Servers Alive only a 200 status code (which is in the
header) is an indication that all is well. (after that we will eventualy still
check the content of the page). Most other status codes are seen as NOT
OK. In the case of a 500 error (that you see in the Servers Alive GUI),
it's the status code (error in this case) we get back from the webserver.
So what we show in the GUI is the status code together with the status string as
send by the webserver.
Some webservers (like IIS) can show more info on the error
within the webpage. We can't give you that full webpage within the
interface. Even within the log that's not realy possible. Remember
that it's possible to adapt the errorpages of your webserver and as such they
could also show non-interesting info.
If you do get an error like the 500 in the Servers Alive
GUI, the best thing you can do is check for yourself that URL too for some more
troubleshooting. Servers Alive is showing you that there is a problem and
gives you the error code.
(some statuscodes like a 302 are not seen as an error
because Servers Alive will interprete this 302 (redirect) and follow the
redirect).
Dirk. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Friday, May 28, 2004 9:18 PM To: [EMAIL PROTECTED] Subject: RE: [SA-list] Show friendly http errors The 500 is the error when get from the webserver within the
header not within the page. We can't change that.
Dirk. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Passow Sent: Friday, May 28, 2004 9:15 PM To: [EMAIL PROTECTED] Subject: RE: [SA-list] Show friendly http errors I got a 500 internal
server error the other day that was due to msado15.dll not being registered
somehow. When turning off show friendly http error messages on my machine
I got an ASP error message with a number that allowed me to find the answer
within 5 minutes on the web. Prior to that I had tried everything to no
avail. Had servers Alive been able to give me the ASP error instead of the
500 internal server error I could have fixed our website before anyone noticed
it was down. From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx What do you mean with
'turn off'? Just say "ERROR"? Dirk. From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Passow I noticed that Salive displays
friendly http errors like internal error 500. Is there a way to turn that
off? Jason
Passow Mississippi Welders Supply
Co. Phone:
507-454-5231 Fax:
507-454-8104 "Evil does
not naturally dwell in the world, in events, or in people. Evil is a by-product
of forgetfulness, laziness, or distraction: it arises when we lose sight of our
true aim in life." -- Epictatus
|
- [SA-list] Show friendly http errors Jason Passow
- RE: [SA-list] Show friendly http errors Dirk Bulinckx
- RE: [SA-list] Show friendly http errors Jason Passow
- RE: [SA-list] Show friendly http errors Dirk Bulinckx
- Dirk Bulinckx
