Error 503 with Firefox only
Originally Posted by Brains
So when this problem occurs, just closing and re-opening Firefox solves the problem?
Now THAT is funny -- someone who says FF is crap, and loves IE 
FF is definitely a better browser than IE, you can't blame it for the faults of some crapware ****-stealing or warez plugins you were trying to run
Originally Posted by Brains
Now THAT is funny -- someone who says FF is crap, and loves IE FF is definitely a better browser than IE, you can't blame it for the faults of some crapware ****-stealing or warez plugins you were trying to run
that ff was stutering on either. It was just common interactions. If you've never had an issue with one product and nothing but issues with the other then you form an opinion of it. I've never had an issue with IE.
Thats not to say others havent, I just havent, but FF on my friends computers sucks *****. Maybe their pc's have issues, that I dont know, but the internet is a nightmare when I use it and try and look at vids or open a site with a plug-in.. like the magnaflow site with interactive sounds.. stuff like that, not warez or ****.. LMAO!!! I've got all the **** I need on my pc and it runs fine
IE is definitely not crap, but it is unfortunately full of security holes that by design are nearly always really BAD holes (due to it's close integration into the OS). Firefox (and many other browsers) by design aren't as risky. IE is also the easiest target.
There CAN be a little more effort involved in getting various things to play, when certain websites decide to use a microsoft-only codec or something of the sort. Even then, I use FF exclusively, not even in the Windows environment (Ubuntu Linux, mostly), and I can play anything you can. My browser never crashes, it doesn't get spyware, I don't get viruses, etc. Heck, I can TRY to open a typical virus sent to all these windows machines, and it won't DO anything on Linux
There CAN be a little more effort involved in getting various things to play, when certain websites decide to use a microsoft-only codec or something of the sort. Even then, I use FF exclusively, not even in the Windows environment (Ubuntu Linux, mostly), and I can play anything you can. My browser never crashes, it doesn't get spyware, I don't get viruses, etc. Heck, I can TRY to open a typical virus sent to all these windows machines, and it won't DO anything on Linux
I've had this problem for a while with FF. Current version is 2.0.0.4 but I've had problems with previous version. Switching immediately to IE works fine. Switching user agents within FF does not solve the problem. I haven't tried clearing the cookie but I'll try that next time it happens and see if I can get a copy for analysis.
LS1 Tech Stories
The Best V8 Stories One Small Block at Time
6 Common C5 Corvette Failures and What's Involved In Repairing Them
Pouria Savadkouei
Retro Modern Bandit Pontiac Trans AM Comes With Burt Reynolds' Autograph
Verdad Gallardo
Top 10 Greatest Cadillac V Series Performance Models Ever, Ranked
Pouria Savadkouei
Top 10 Most Powerful Chevy Trucks Ever Made!
Hennessey's New Supercharged Silverado ZR2 Has 700 HP
Verdad Gallardo
Coachbuilt N2A Anteros Is an LS2-Powered C6 Corvette In Italian Clothes
Verdad Gallardo
Awesome K5 Blazer Restomod Comes With C7 Corvette Power
Verdad Gallardo
10 Camaros You Should Never Buy
10 LS Engine Myths That Refuse to Die
Verdad Gallardo I don't know what you guys are doing, but I have *NEVER* cleared cookies in FF, on any machine, on either Windows or Linux. I had to do it every now and then in IE when it would refuse to update them, but that was pretty rare as well.
Honestly, I'd be willing to wager some of you guys are surfing sites and/or installing software that do their best to "crack" systems and exploit their weaknesses. You should EXPECT your system to catch something when you're hanging out in the gutter Many **** sites, warez sites, peer-to-peer software packages, etc. are in the popular list.
Honestly, I'd be willing to wager some of you guys are surfing sites and/or installing software that do their best to "crack" systems and exploit their weaknesses. You should EXPECT your system to catch something when you're hanging out in the gutter
Many **** sites, warez sites, peer-to-peer software packages, etc. are in the popular list.
Originally Posted by Brains
I don't know what you guys are doing, but I have *NEVER* cleared cookies in FF, on any machine, on either Windows or Linux. I had to do it every now and then in IE when it would refuse to update them, but that was pretty rare as well.
Honestly, I'd be willing to wager some of you guys are surfing sites and/or installing software that do their best to "crack" systems and exploit their weaknesses. You should EXPECT your system to catch something when you're hanging out in the gutter Many **** sites, warez sites, peer-to-peer software packages, etc. are in the popular list.
Honestly, I'd be willing to wager some of you guys are surfing sites and/or installing software that do their best to "crack" systems and exploit their weaknesses. You should EXPECT your system to catch something when you're hanging out in the gutter
Many **** sites, warez sites, peer-to-peer software packages, etc. are in the popular list.
Originally Posted by Brains
You should EXPECT your system to catch something when you're hanging out in the gutter
Actually, this is a vanilla install. The only thing I've added was the useragent switcher which I added to see if it was a useragent problem only (because IE worked when FF didn't). This box was blown away about 3 weeks ago. Unless the error was customized, 503 generally means the server took too long to respond. The interesting thing is it's an error page returned by the server. I'm guessing there is a server side script that handles firefox differently or something that isn't rendering well within firefox. It doesn't happen all the time but when it does, it's pretty steady. I'll see if I can collect some information. Hell it might have something to do with your permissions on the board. Maybe create and surf from a normal user account try that for a while?
The two boxes I've noticed it on is my wife's Dell running SP2 and Firefox (unsure of version but I think it's a couple revisions old) and my IBM T42 laptop also running SP2 running Firefox v2.0.0.4. I seen .5 came out so I am going to upgrade to that and see if it makes any difference. Anyway, hope this helps.
If it were a server problem, it would affect everyone using Firefox -- and I've *never* seen a 503 error on 'Tech. The further odd thing is, you're absolutely correct -- 503 is a server generated message, and thus should then affect *ALL* browsers. Yet, you guys are saying you're seeing this exclusively with one family of browsers.
The actual description for the 503 is:
So, the next question is, are you seeing this message after 60 seconds (the timeout value) or immediately?
The actual description for the 503 is:
Initial Request Timeout
Description: Specifies the maximum time the web server waits for the external application to respond to the first request over a new established connection. If the web server does not receive any data from the external application within this timeout limit, it will mark this connection as bad. This helps to identify communication problem with external application as quickly as possible. If some requests take longer time to process, increase this limit to avoid "503" error messages.
Description: Specifies the maximum time the web server waits for the external application to respond to the first request over a new established connection. If the web server does not receive any data from the external application within this timeout limit, it will mark this connection as bad. This helps to identify communication problem with external application as quickly as possible. If some requests take longer time to process, increase this limit to avoid "503" error messages.
Brains, even on my computer FF has had issues with this last release. It's windows specific as I have no issues with FF on Ubuntu feisty on my POS 8 yo laptop. They fucked something up this go around and its not cool.
FF is still the best browser I've used though. IE7 is a steaming pile of cow dung.
I get a lot of errors on Netscape and IE on my work computer, but that has to do with my craptastic internet connection. I don't recall getting a 503 on either browser through while trying to surf 'tech.
FF is still the best browser I've used though. IE7 is a steaming pile of cow dung.
I get a lot of errors on Netscape and IE on my work computer, but that has to do with my craptastic internet connection. I don't recall getting a 503 on either browser through while trying to surf 'tech.
Originally Posted by Brains
If it were a server problem, it would affect everyone using Firefox -- and I've *never* seen a 503 error on 'Tech. The further odd thing is, you're absolutely correct -- 503 is a server generated message, and thus should then affect *ALL* browsers. Yet, you guys are saying you're seeing this exclusively with one family of browsers.
The actual description for the 503 is:
So, the next question is, are you seeing this message after 60 seconds (the timeout value) or immediately?
The actual description for the 503 is:
So, the next question is, are you seeing this message after 60 seconds (the timeout value) or immediately?
When it happens to me, it returns very nearly immediately. I am with cyphur in that I haven't seen it on any of my Xix boxes running firefox. But the error page is definately being returned by the server (Lightspeed webserver as it appears in this case). It's not local.
I agree that it is strange that it is only affecting one family of browsers (and ironically, it's not IE this time). It 'feels' like something in the server side scripts is puking on the the request from a firefox client? I can't imagine what but is there any major delineation between browsers when checks are performed? I honestly haven't noted anything special I was doing that is different than any other time. I will say I seem to notice it more when clicking on posts in the classifieds. The forum will render fine but clicking on individual threads is where the error always occurs for me.
Tech is the only vbulletin board I've noticed it on. Is there a ton of custom code running?
haha...the lovely 503...native to apache and IIS 6.0
argue what you may, this has nothing to do with cache...it doesn't even make sense how the hell it would even be in conjunction with cache. Firefox, IE...hell, Opera or ANY browser can return this message.
The 503 is a server busy message...nothing more, nothing less. Nothing fancy.
I know for a fact when I'm on the site at crunch (usually around 6-10PM EST) it dogs like crazy as everyone else is on which can throw this at any given moment.
argue what you may, this has nothing to do with cache...it doesn't even make sense how the hell it would even be in conjunction with cache. Firefox, IE...hell, Opera or ANY browser can return this message.
The 503 is a server busy message...nothing more, nothing less. Nothing fancy.
I know for a fact when I'm on the site at crunch (usually around 6-10PM EST) it dogs like crazy as everyone else is on which can throw this at any given moment.
I don't run the latest version of Firefox, but I do run it exclusively. I've never seen a 503 either.
I have received 408's - timeouts. That's when the site is slowing to a crawl and things go down the tubes. That's when "Speeddial - Brains" on my cellphone comes in handy.
I have received 408's - timeouts. That's when the site is slowing to a crawl and things go down the tubes. That's when "Speeddial - Brains" on my cellphone comes in handy.
Originally Posted by phrozen755
haha...the lovely 503...native to apache and IIS 6.0
Originally Posted by phrozen755
The 503 is a server busy message...nothing more, nothing less. Nothing fancy.
Originally Posted by phrozen755
I know for a fact when I'm on the site at crunch (usually around 6-10PM EST) it dogs like crazy as everyone else is on which can throw this at any given moment.
Thread Starter
TECH Fanatic
iTrader: (11)
Joined: Nov 2003
Posts: 1,781
Likes: 0
From: Marysville, WA
My errors also show up immediately, there is no timeout delay. I have been on this site for years using exclusively FF, and the 503 error has only appeared recently. No other new info at this time.
I also started receiving this error today here's a print screen, clearing out the cookies seemed to work, it only happened when I try to open a thread:
http://s117.photobucket.com/albums/o...rent=error.jpg
http://s117.photobucket.com/albums/o...rent=error.jpg