Blog Documentation Book a Demo

Can't View Vanilla Forums On Firefox 1.5.0.1

seunosewaseunosewa
edited February 2006 in Vanilla 1.0 Help
Hello, Ever since I upgraded to Firefox 1.5.0.1 I have been unable to visit any forums using Vanilla from Firefox. The page just doesn't show and displays no error message. Anyone experiencing similar problems? Seun.

Comments

  • MarkMark Vanilla Staff
    The only thing I can suggest is clearing your cookies. I'm using ff1.5.0.1 now and it works just fine.
  • ithcyithcy New
    i'm using 1.5.0.1 also, no problems
  • seunosewaseunosewa
    I did some further research, and I notice that there are other sites I cannot open with my Firefox browser for some reason: An example is www.domainsite.com. I checked the headers and I think that the problem may lie in the headers, which are quite similar for my installed forum and the domainsite. ===Domainsite HTTP/1.x 200 OK Transfer-Encoding: chunked Date: Fri, 10 Feb 2006 04:34:03 GMT Content-Type: text/html; charset=UTF-8 Expires: Fri, 10 Feb 2006 04:34:03 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Server: Apache X-Powered-By: PHP/5.0.2 Set-Cookie: PHPSESSIDWEB2=96917a342f2ffd2de890d2935527ea76; path=/; domain=domainsite.com Pragma: no-cache Via: 1.1 speed (NetCache NetApp/6.0.1) ===Vanilla Forum HTTP/1.x 200 OK Transfer-Encoding: chunked Date: Fri, 10 Feb 2006 04:29:35 GMT Content-Type: text/html; charset=utf-8 Expires: Fri, 10 Feb 2006 04:29:35 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Server: Apache/2.0.54 (Debian GNU/Linux) DAV/2 SVN/1.1.4 PHP/4.3.10-16 mod_ssl/2.0.54 OpenSSL/0.9.7e X-Powered-By: PHP/4.3.10-16 Last-Modified: Fri, 10 Feb 2006 04:29:35 GMT Pragma: no-cache Via: 1.1 speed (NetCache NetApp/6.0.1) === I would like to know how I can change the headers, for instance the line "Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0" Thanks.
  • lechlech ✭
    Are you using any silly extensions like adblock or greasemonkey with possibly bad filters/formatters? Because that could be and always seems to be a likely first suspect in these matters. The headers that you're seeing there are generated for vanilla via apache + php by the looks of it, I wouldn't mess with them unless you know what you're doing. As a last resort, double check to see if you have your cache even enabled. If you're using the webdev toolbar, it's under the disable option/icon.
This discussion has been closed.