im running mozilla 1.0.1 both at home and at work. my work install has developed a nasty habit of throwing a 'this document contains no data' 1 time for every 2 or 3 pages i visit. refreshing or clicking the link again brings the page right up with no problem. now at first it would take friggin forever before throwing that message and i could tell it was going to happen. now, it throws the error quite quickly. i get the message absolutely everywhere i go.
ie works just fine on the same system and theyre configured with identical proxy information. i have been all over mozillas config options and i cannot find any reason why this should be happening. i uninstalled and reinstalled using moz 1.2.1 and that has the same problem.
any ideas? i got nothin.
~james
I was having some annoying problem in Mozilla after upgrading a while back, but I can't remember what it was. I upgraded to the newest version and it still happened. Then I downgraded to the original 1.0 and it still happened.
I had to completely uninstall Mozilla, delete my Mozilla profile, and reinstall it before it went away. Maybe just creating a new profile would have worked, I dunno.
I see that occasionally on 1.0.1, but nowhere near as often as you describe. Do you have HTTP pipelining turned on?
I've enountered that problem in phoenix a couple times. I've had more problems with java than anything lately though. Can't figure that one out. Too busy to take the time though.
Originally posted by MaggieL
I see that occasionally on 1.0.1, but nowhere near as often as you describe. Do you have HTTP pipelining turned on?
nope. i enabled it and will see how it goes.
~james
Originally posted by perth
nope. i enabled it and will see how it goes.
Erk...I didn't mean "turn it on". I was just wondering if that was *causing* the problem. I would expect piplining to cause you some problems, since some servers don't support it.
I've also seen Moz 1.0.1 pick up the wrong MIME type sometimes on a download. Sometimes it seems to think everything is a JPEG.
well, for what its worth, i have not seen the error in the 1/2 hour since i switched it on. ill experiment. i dont really understand what it is or how it works, so its probably just coincidence.
the problem happens with every website i generally visit, including the cellar.
worst case, i may nuke the install and profile, make sure the registry is clean and install 1.2.1 to see how it goes. but i hate those shotgun approaches to solving a problem.
~james
Originally posted by perth
well, for what its worth, i have not seen the error in the 1/2 hour since i switched it on. ill experiment. i dont really understand what it is or how it works, so its probably just coincidence. ...
spoke too soon. think ill try the less-than-subtle approach. :)
~james
Seen it in phoenix a few times, but not since .4
Perhaps you have run across
this bug?
Other posts on usenet suggest clearing your cache. Have you tried that?
yeah. whatever it was, the shotgun approach seemed to work, knock on wood.
~james
Originally posted by juju
Perhaps you have run across this bug?
Speaking as somebody with fairly extensive experience in development, support and QA roles in computing, that Bugzilla entry is so beautiful it brings a tear to my eye. Having an highly intelligent user on the problem end, a *very* freaking obscure bug is nailed in an exceedingly short period of time.
*That* is what open source is all about.
Hey! I know! Why doesn't somebody ask Radar? He's an MCSE, after all. ;)
But IE doesn't have bugs, its the best browser ever produced! Not only is it the most stable, but its far more user friendly too! If you pay enough they'll teach you anything.
Originally posted by MaggieL
...that Bugzilla entry is so beautiful it brings a tear to my eye.
Yes, it was handled well, but holy cripes! Multiple POST requests when submitting forms?!
I think I'll seriously reconsider using Mozilla/Phoenix for online purchases...
Originally posted by Tobiasly
Yes, it was handled well, but holy cripes! Multiple POST requests when submitting forms?!I think I'll seriously reconsider using Mozilla/Phoenix for online purchases...
Well, when you screw up that far down in the stack, bad shit can happen. It's a *very* obscure bug.