Learn More. Chosen solution In Firefox it is called the cache, for details of its location type about:cache into the location bar and press enter. TonyE Moderator. Chosen Solution In Firefox it is called the cache, for details of its location type about:cache into the location bar and press enter.
In Firefox it is called the cache, for details of its location type '''about:cache''' into the location bar and press enter.
Ahmed57 Question owner. Thanks everybody for helping this question. I believe I found the reason why FireFox seems very slow on window 7 box. I did not notice the slowness when I was using windows XP. First all, Firefox will NOT cache any resource from asp. When I use firebug check the resource downloading today, I noticed DNS lookup takes a couple of seconds.
If you would be set additionally ETag in the header with some your custom checksum of hash from the data, the ETag from the previous request will be sent to the server. The server are able either to return the data or, in case that the data are exactly the same as before, it can return empty body and HttpStatusCode.
NotModified as the status code. In the case the web browser will get the data from the local browser cache. I recommend you to use Cache-Control: private which force two important things: 1 switch off caching the data on the proxy, which has sometimes very aggressive caching settings 2 it will allows the caching of the the data, but not permit sharing of the cache with another users. It can solve privacy problems because the data which you return to one user could be not allowed to read by another users.
By the way the code HttpContext. Public ; to overwrite the behavior or use Headers. Set instead of Cache. If you have interest to study more caching options of HTTP protocol I would recommend you to read the caching tutorial.
Corresponds to the information from the Wikipedia even so old web browsers like Mosaic 2. In any way Netscape 2. So you should ask you first: which HTML standards you use? Do you still use HTML 2. I suppose you use at least HTML 4. So if you build your application at least in HTML 4. Including of the headers is in my opinion is pure paranoia. As I have some caching problem myself I tried also to include different other headers, but later after reading carefully the section The only "Cache-Control" header which can be additionally discussed is "must-revalidate" described on the section Here is the quote:.
The must-revalidate directive is necessary to support reliable operation for certain protocol features. Servers SHOULD send the must-revalidate directive if and only if failure to revalidate a request on the entity could result in incorrect operation, such as a silently unexecuted financial transaction.
Although this is not recommended, user agents operating under severe connectivity constraints MAY violate this directive but, if so, MUST explicitly warn the user that an unvalidated response has been provided. Sometime if I have problem with Internet connection I see the empty page with "Gateway Timeout" message. Pavlo I did doubt that was not take from cache,but it's an old version Firebug and I found out that when it was grey not the black ,it did load from cache.
That version of Firefox is unsupported End-of-Life anyway. I agreed with your guess. However, I disabled memory cache or disk memory and can't find anything special happened.
My physical memory is enough. Add a comment. Active Oldest Votes. So the time is so slow. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog.
0コメント