Error Loading Content Ns_error_document_not_cached
Contents |
Sign in Pricing Blog Support Search GitHub This repository Watch 0 Star 0 Fork 0 jbrozenick/httpfox Code Issues 86 Pull requests 0 Projects
Ajax Error Loading Content Ns_error_document_not_cached
0 Pulse Graphs New issue "Content" tab issues NS_ERROR_DOCUMENT_NOT_CACHED on all POST/GET fehler beim laden des contents ns_error_document_not_cached in nightly FF3 builds : ( #20 Open GoogleCodeExporter opened this Issue Jun 12, 2015 · 20 comments Projects None yet Labels auto-migrated Priority-Medium Type-Defect Milestone No milestone Assignees No one assigned 1 participant GoogleCodeExporter commented Jun 12, 2015 What steps will reproduce the problem? 1. Get the Firefox 3 Nightly build (tested with Gecko/2008051006) 2. Run any POST or GET request 3. What is the expected output? What do you see instead? expected the "Content" tab to display the responseXML/responseText, it displays "Error loading content (NS_ERROR_DOCUMENT_NOT_CACHED)" What version of the product are you using? On what operating system? Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9pre) Gecko/2008051006 Minefield/3.0pre Please provide any additional information below. hopwe this is an easy fix :) very sad to have found it to replace bulky Firebug to find out it doesnt work :(. Original issue reported on code.google.com by leeon...@gmail.com on 10 May 2008 at 6:47 GoogleCodeExporter commented Jun 12, 2015 please check the following firefox preferences: (this can be done with the "about:config" url) 1) browser.cache.disk.enable make sure this is set to "true" (default: true) 2) browser.cache.memory.enable make sure this is set to "true" (default: true) 3) network.http.use-cache make sure this is set to "true" (default: true) 4) browser.cache.disk_cache_ssl setting this to "true" should help getting the content of https requests. it is deactivated by default for security reasons. (default: false) (see http://kb.mozillazine.org/Browser.cache.disk_cache_ssl) Original comment by pappkame...@gmail.com on 12 May 2008 at 10:55 Changed state: Accepted GoogleCodeExporter commented Jun 12, 2015 I am using the Web Developer add-on and had its Disable Caching option turned on, which was the reason these settings were user configured rather than at the defaults, so watch
Sign in Pricing Blog Support Search GitHub This repository Watch 0 Star 0 Fork 1 jaim8682/httpfox Code Issues 86 Pull requests 0 Projects 0 Pulse Graphs New issue NS_ERROR_DOCUMENT_NOT_CACHED #120 Open GoogleCodeExporter opened this Issue Dec 31, 2015 · 1 comment Projects None yet Labels auto-migrated Milestone No milestone Assignees No one assigned 1 participant GoogleCodeExporter commented Dec 31, 2015 What steps will reproduce the problem? 1. Get the Firefox 13.0.1 2. Run jQuery AJAX GET request 3. What is the expected output? What do you https://github.com/jbrozenick/httpfox/issues/20 see instead? Response of server side script What version of the product are you using? On what operating system? HttpFox 0.8.11, Firefox 13.0.1, Windows 7 Professional SP1 Please provide any additional information below. Hi, sometimes I get this message: Error loading content (NS_ERROR_DOCUMENT_NOT_CACHED) when I click in "Content" tab in a GET request. I have checked below settings, and everything is like said https://github.com/jaim8682/httpfox/issues/120 1) browser.cache.disk.enable make sure this is set to "true" (default: true) 2) browser.cache.memory.enable make sure this is set to "true" (default: true) 3) network.http.use-cache make sure this is set to "true" (default: true) 4) browser.cache.disk_cache_ssl setting this to "true" should help getting the content of https requests. it is deactivated by default for security reasons. (default: false) Congrats for the work, this is a great addon, would be better without this bug (if it is a bug..) Original issue reported on code.google.com by glauco.c...@gmail.com on 26 Jun 2012 at 5:48 GoogleCodeExporter commented Dec 31, 2015 Just empty the Firefox cache in Tools->Options However, this does not work anymore in FF19 Original comment by dau.muie...@gmail.com on 6 Mar 2013 at 4:20 GoogleCodeExporter added the auto-migrated label Dec 31, 2015 Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment Contact GitHub API Training Shop Blog About © 2016 GitHub, Inc. Terms Privacy Security Status Help You can't perform that action at this time. You signed in with another tab or window. Reload to refresh your session. You signed out
New? Today's Posts FAQ Rules Guidelines Search Advanced Search Forum :: Client side development General web building Browser caching problem - POST If this is your first visit, be sure to http://www.codingforums.com/general-web-building/210393-browser-caching-problem-post.html check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Enjoy an ad free experience by logging in. Not a member yet? Register. Results 1 to 5 of 5 Thread: Browser caching problem - POST Thread Tools error loading Show Printable Version Email this Page… Subscribe to this Thread… Rate This Thread Current Rating Excellent Good Average Bad Terrible 11-27-2010,06:45 AM #1 bokfok View Profile View Forum Posts New to the CF scene Join Date Nov 2010 Posts 1 Thanks 0 Thanked 0 Times in 0 Posts Browser caching problem - POST I have a Javascript file that interacts with a PHP server side script via a POST error loading content using AJAX. The JS is executed when an item is selected from a drop down (SELECT) and triggers the PHP file (guardIFRAMEroster.php), posting to it parameters configured by the JS based on the selection made from the drop down (SELECT). The PHP scipt file then outputs HTML to an iFrame that forms part of the current page loaded by the browser. As part of loading the page from which all of this is driven, the PHP script file (that constructs the iFrame HTML content) is retrieved by the browser (with no qualifying parameters) via GET. So, when the page that “owns” the iFrame is loaded, the PHP script file is read from the server via GET as well. The response to this GET from the PHP script is invalid/incomplete at this point as no qualifying parameters were included as part of the call to the server. At this stage this is not an issue as the iFrame is not initially displayed and only becomes viewable once a selection is made from the drop down list (SELECT). This (GET image) seems to be the cause of the subsequent cache issue described here after. By the time the POST is done to the PHP serv