Msg#: 3328015 posted 11:24 pm on May 1, 2007 (gmt 0)
I was trying to look for clues why my site went down today (for 2 hours) and noticed that the log showed there was plenty of traffic during that time.
My host has a server status page, and there were some areas of red for my server, so it couldn't have been just me not being able to access the site (right?). And I realize that some people may be getting through ok depending on when they hit the site. But not only am I seeing "normal" traffic patterns during the outage, but I'm seeing status 200 codes for my own IP address when I know I didn't get through (to my website admin area so I know it is me).
Msg#: 3328015 posted 12:11 pm on May 3, 2007 (gmt 0)
Welcome to Webmasterworld, MsCarpetbagger. I hope you visit often.
Your problem sounds more like a router problem than a server problem. It appears that the page requests were getting to the server (because they showed up in the server logs), but for some reason the response didn't make it back to you. A misconfigured or downed router (not necessarily at your webhost) could have been the culprit, which means that other visitors may have been getting through OK.
When looking at your logs, do you see visitors making requests for the other components of your page (CSS files, images, etc.) If so, they were getting through OK. If all you see are requests for the page (perhaps repeated ones as the user retries the request), then they weren't getting through properly.
Msg#: 3328015 posted 9:51 am on May 7, 2007 (gmt 0)
What error did your browser show? If you wait for say 1 minute, and then leave the page it may still be a HTTP 200 response that just never makes it to your browser in due time. IIS logfiles have a "time-taken" column that can show you how long time the page took to render. Have you got such data?
Msg#: 3328015 posted 9:13 pm on May 7, 2007 (gmt 0)
No, I don't believe I have a "time-taken" column. I think it just timed out on the browser.
The thing that is confusing, though, is that the server status page showed that the server had trouble. So if http was down, or another aspect of the site, then how could all the codes be 200? Would it not return a different code?