Problem with GTAF or Firefox?

[Vanillainy]

So, Im browsing the sex machine that is GTAForums.com (you may of heard of it), but sometimes. If I click a link to another section on the side or refresh the page, either with the refresh button or F5, I get this:

 

(This was from just entering a topic and pressing refresh a few times)

 

Now, it doesn't happen all the time I refresh or click links, it just seems to do at random. Any ideas? it only happens on GTAF, not getting it anywhere else. Its just rather annoying considering I haven't chosen to open index.php, STOP TELLING ME I HAVE.

 

 

[[CTD]LaBan]

there are no problems on my firefox browser. all is working fine.

[SWEETSAPRIK]

 

Its just rather annoying considering I haven't chosen to open index.php, STOP TELLING ME I HAVE. 

Technically you have, look at the links you're clicking.

 

That said, something similar to this has happened to me on one other site, but never here. Not sure why it's happening to you. On the other site it was the site itself having a problem, but since it's not happening to me here, I have no idea what the deal is.

 

This is the only thing I found. Doesn't look like it'll help though.

http://forum.kaspersky.com/index.php?showtopic=51905

 

[Ring_of_Fire]

You could try clearing the cache (Temporary Internet Files) and the Cookies. Also, try resetting the browser to the factory defaults and if that doesn't work, then uninstall/reinstall Firefox. http://www.mozilla.com/en-US/firefox/

 

If still no luck, then there's a program conflicting with Firefox. It's probably an addon/plugin that you need to disable or the link that Sweets mentioned -> http://forum.kaspersky.com/index.php?showtopic=51905 Not sure if an antivirus/spyware/firewall can cause it though.

[Otter]

 

http://readlist.com/lists/lists.debian.org...r/17/88911.html

Edited December 24, 2007 by Otter

[derty]

Yep. The old firefox is trying to nab the index.php bug.

 

I've got this really awesome extension that makes it quick and easy when

coupled with the automatic cleaning options firefox has. It's a simple restart

switch added to the Tools menu, but can be added to other places easily.

 

It's called QuickRestart, and it can be found here.

 

-derty

[Ring_of_Fire]

http://readlist.com/lists/lists.debian.org...r/17/88911.html -> So my recommendation was correct, clear the Firefox cache! I thought I knew nothing about computers?

 

 

You could try clearing the cache (Temporary Internet Files)

[Otter]

http://readlist.com/lists/lists.debian.org...r/17/88911.html -> So my recommendation was correct, clear the Firefox cache! I thought I knew nothing about computers?

 

 

You could try clearing the cache (Temporary Internet Files)

Yeah, note the ninja smiley.

[Vanillainy]

So my recommendation was correct, clear the Firefox cache!

 

Yeah, that didn't work. And I clear it pretty much every day.

[Saggy]

Usually when you contact the forums, you request "index.php". When the server receives the request to the php file, the php file then executes the actions that are inside of it. That's what generates the html for the pages.

 

What's happening is that the server thinks you're requesting the "index.php" file for download instead of trying to execute it. Generally the cookies you have on your computer tell the server whether to run the file or to offer it for downloading ( the cookies don't really dictate this, rather they just have settings in them that the server then decides based off of ), so that's why clearing your cookies and cache sometimes helps, but then other times its something wrong with the server.

 

 

Are you sure you tried clearing your cookies too? The cache and your cookies are two different things. The cache doesn't necessarily cause this, it just makes it worse. The first time you make a request to "index.php" and it tries to save the file instead of executing it, its saved itself to your cache in a way that every time you click "index.php" without clearing your cache, it will try to download the "index.php" out of your cache instead of actually making a request to the server; because you probably don't have php installed on your computer, it will simply bring up a "save" dialog again instead of trying to execute or even making a request to the server to execute. If you clear your cache, and still have the cookies that originally caused the "index.php" file to not to be executed," it will once again request "index.php" as a file to be downloaded instead of executed, and then be stored into your cache once again. It's very important to clear cookies and your cache if this is happening.

 

If clearing your cookies doesn't help, there may not be a lot you can do, because generally problem with php are server-side issues. As for why no one else is having the problem, I've experienced this problem on GTAF once or twice, but not frequently at all. Are there any special settings that you have enabled that might cause you to get different cookies than the rest of the members?

 

Edit

 

Heh, what a coincidence, it just happened to me. Seems like a server-side issue.

Edited December 25, 2007 by SagaciousKJB

[Vanillainy]

Usually when you contact the forums, you request "index.php". When the server receives the request to the php file, the php file then executes the actions that are inside of it. That's what generates the html for the pages.

 

What's happening is that the server thinks you're requesting the "index.php" file for download instead of trying to execute it. Generally the cookies you have on your computer tell the server whether to run the file or to offer it for downloading ( the cookies don't really dictate this, rather they just have settings in them that the server then decides based off of ), so that's why clearing your cookies and cache sometimes helps, but then other times its something wrong with the server.

 

 

Are you sure you tried clearing your cookies too? The cache and your cookies are two different things. The cache doesn't necessarily cause this, it just makes it worse. The first time you make a request to "index.php" and it tries to save the file instead of executing it, its saved itself to your cache in a way that every time you click "index.php" without clearing your cache, it will try to download the "index.php" out of your cache instead of actually making a request to the server; because you probably don't have php installed on your computer, it will simply bring up a "save" dialog again instead of trying to execute or even making a request to the server to execute. If you clear your cache, and still have the cookies that originally caused the "index.php" file to not to be executed," it will once again request "index.php" as a file to be downloaded instead of executed, and then be stored into your cache once again. It's very important to clear cookies and your cache if this is happening.

 

If clearing your cookies doesn't help, there may not be a lot you can do, because generally problem with php are server-side issues. As for why no one else is having the problem, I've experienced this problem on GTAF once or twice, but not frequently at all. Are there any special settings that you have enabled that might cause you to get different cookies than the rest of the members?

 

Edit

 

Heh, what a coincidence, it just happened to me. Seems like a server-side issue.

Thanks for that, I understand it now.

 

I cleared my cookies now, usually I just press clear now, but that didn't include cookies. So I've included cookies and it hasn't happened for a while now. Suppose I'll have to give it some time, hopefully it has stopped.

[Svip]

Usually when you contact the forums, you request "index.php". When the server receives the request to the php file, the php file then executes the actions that are inside of it. That's what generates the html for the pages.

 

What's happening is that the server thinks you're requesting the "index.php" file for download instead of trying to execute it. Generally the cookies you have on your computer tell the server whether to run the file or to offer it for downloading ( the cookies don't really dictate this, rather they just have settings in them that the server then decides based off of ), so that's why clearing your cookies and cache sometimes helps, but then other times its something wrong with the server.

No no no. You cannot request a file for downloading like that. The server will all the time attempt to execute the script and send it to you. But if something happens along the way during the execution, and the output becomes ill, the server will have to assume the content-type header for it. And sometimes, it gets it wrong.

 

So when the browser sees that the content-type is not "text/html", but rather something else, the browser thinks its a file that it cannot display.

 

IE does not do that, because it "sniffs" the files, so it attempts to see if the server did something wrong. While it may seem like a good idea in this case, it does f*ck up a lot of text based stuff which is supposed to be text/plain, but due to the sniffing, IE starts rendering it as text/html, and it starts looking all wrong.

[Saggy]

Usually when you contact the forums, you request "index.php".  When the server receives the request to the php file, the php file then executes the actions that are inside of it.  That's what generates the html for the pages.

 

What's happening is that the server thinks you're requesting the "index.php" file for download instead of trying to execute it.  Generally the cookies you have on your computer tell the server whether to run the file or to offer it for downloading ( the cookies don't really dictate this, rather they just have settings in them that the server then decides based off of ), so that's why clearing your cookies and cache sometimes helps, but then other times its something wrong with the server.

No no no. You cannot request a file for downloading like that. The server will all the time attempt to execute the script and send it to you. But if something happens along the way during the execution, and the output becomes ill, the server will have to assume the content-type header for it. And sometimes, it gets it wrong.

 

So when the browser sees that the content-type is not "text/html", but rather something else, the browser thinks its a file that it cannot display.

 

IE does not do that, because it "sniffs" the files, so it attempts to see if the server did something wrong. While it may seem like a good idea in this case, it does f*ck up a lot of text based stuff which is supposed to be text/plain, but due to the sniffing, IE starts rendering it as text/html, and it starts looking all wrong.

Hmm, well, I guess that explains what is actually going on with it, but I always figured it was just the cookies causing the server to either offer it for download or as a script based off observation. Is it still the cookies that mostly cause this? Clearing them seems to be the universal solution whenever it happens to me on FireFox. I suppose there's a multitude of things that could be the cause, but I'm wondering if my assumption about the cache not having anything to do with it is right.

 

 

Thankfully clearing cookies seems to help on the very rare instances where this happens.