HTTP 408/409 Error

[wild_bill]

I just recieved an error:
The website is too busy to show the webpage
HTTP 408/HTTP 409

I refreshed and everything is fine, but I thought you folks might want a heads up.

[Justa Lol]

i don't think this is an error since it basically means the connection timed out, could be heavy traffic...

http://en.wikipedia.org/wiki/List_of_HTTP_status_codes

[brad jones]

Has, is, or did anyone else get this error as well?

Brad!

[Shaggy Hiker]

I have seen this message a few times over the last couple weeks. Oddly, it happens very quickly when it does happen.

[Shaggy Hiker]

This error is coming up much more often over the last week. It happens pretty much every time I visit the site, and about every 10-20 pages, or so. Oddly, when it happens, it is nearly instantaneous. There is never a delay that results in this error. It comes back faster than any thread.

[EntityX]

I see this error on a regular basis. Seems like since a month or 2 back I started seeing it. Perhaps something should be done so that the site can handle more traffic. I get the same response as Shaggy. There is no timing out but an immediate or fairly quick showing of the error page saying the website is too busy.

[brad jones]

Hmmm..... My techie guys say "It is a client side issue."

Our servers aren't showing slowdowns that I'm aware of. If you guys get this again, send me an email when it is happening. (Webmaster@ this domain).

Thanks,

Brad!

[Shaggy Hiker]

This response, when it happens, is instantaneous. It's faster than any web page. However, since your techie guy suggests that it is client side, there is something for me to look at. I am running a couple different browsers. It is possible that this problem has happened on only one of them. I'll keep track of it to see if it is browser or system related.

[EntityX]

At one point I was seeing that message quite a bit. I have wireless internet. There's a transceiver that is mounted on my garage. I was having a good deal of interruption and down time in my internet service and I was investigating various options to solve the problem. I decided to try elevating the transceiver on my garage in the hope that it would get a stronger signal from the other transceiver that it was communicating with. I put up a taller mast on my garage and raised the transciever something like 3 feet higher. I noticed I was getting one more signal strength LED lighting up and now my connection is noticeably better. Before the improvement in service I saw that HTTP 408/409 Error quite a bit and since the improvement I see it quite a bit less but I still see it on a regular basis. This would support what your "techie guy" says that it is a client side issue. So the question is what can we do on our end to see it less or not at all apart from improving one's wireless internet connection. I've been using IE9 when I see the error. I also have Google Chrome and Firefox so I could start using those and see if it disappears. wild bill and Shaggy were you guys using IE9?

[Shaggy Hiker]

It is becoming increasingly clear that the error was not random, but was isolated to just one machine running IE 9. I think I'll switch to Chrome, as that will probably cause it to go away.

[techgnome]

Nope... I get it on Chrome too... one thing though, it's always when trying to view a thread... never happens on the search userpanel or any where else. And as SH notes, it happens quick, so it's not like there's a delay and then it shows up... just BAM! and there it is. I just refresh or go back and hit the link a second time, and it works.

-tg

[Shaggy Hiker]

Yeah, I've now gotten it on Chrome, too. I've gotten it when I tried to go into the .NET forum from the first page, so not always a thread, for me.

[techgnome]

I don't know what's going on, but the site has been running slow since about 10am EDST ... getting progressively worse... and just a couple minutes ago while trying to quick reply to a post, it completely wrecked my browser to the point where end tasking it was the only way to regain control.

As it was, it then took another 5 minutes to get into this thread.

[acb123]

anyone remember what resolved this issue?

[Shaggy Hiker]

Nothing resolved this issue, it still happens. It's just not all that frequent, it's fast, and it's easy to deal with.