Journal FortKnox's Journal: 503 Fix (UPDATED) 17
Annoying as hell, but if you delete your cookies for slashdot and relogin, you usually can avoid 503's as long as your session stays live (some bored people figured it out and posted it to slashdot's bug tracker). But if the system has to log you in based on your cookie, it'll die. Hope that helps your browsing experience, and makes you laugh at someone who has had a major website up for countless years still doesn't know how to handle cookies.
Update: Got the word from pudge himself. Cookies aren't the problem (actually, I believe the words were, Cookies aren't the problem... ignore fortknox and listen to sllort (I can't believe I just said that :-). Sllort had just mentioned after me that cookies weren't the problem). Guess my credibility has gone downhill since I've been put in "The List" in Trollback... ;-)
Update: Got the word from pudge himself. Cookies aren't the problem (actually, I believe the words were, Cookies aren't the problem... ignore fortknox and listen to sllort (I can't believe I just said that
D (Score:2)
It logged me in, even though the login page hasn't actually loaded. I'll stick with https, which gives me the lowest 503/page ratio.
*Clears throat*
GAH~!
S also keeps me from browsing at the speed of bleeding out through a hangnail.
Re: D (Score:1)
Joy...
I'm just amused (Score:2)
Re:I'm just amused (Score:1)
Re:I'm just amused (Score:2)
If development for the new site falls under any of the rules, someone email me and smack me around.
This is easy (Score:2)
If risks are reviewed once every other week (I'm assuming the dev pace on the new system will be a bit slower than a paid-for project, because we all gotta eat), that should be sufficient to prevent risk realization.
Re:This is easy (Score:2)
Something else that's funny... (Score:2)
But I'll bet the lost ad revenue is killing them. Can't see the page, can't see the ads. That hits them where it hurts.
Re:Something else that's funny... (Score:1)
are we there yet? (Score:1)
Re:are we there yet? (Score:1)
Re:are we there yet? (Score:2)
The real 503 Fix (Score:1)
Anyhow the real fix is to view slashdot in Communicator 4.78...I have not had a single 503 error since loading it up in Netscape 4.78.
Re:The real 503 Fix (Score:1)
I'll bet most of you (Score:2)
tap
tap
tap
has it been 20 seconds yet?
Didn't see this fix (Score:2)