| .NET DotNet Forum Index » ASP.NET Forum » Age expires... |
|
Page 1 of 1 |
|
| Author |
Message |
| 3P... |
 Posted: Thu Nov 05, 2009 2:47 pm |
|
|
|
Guest
|
Hi.
Can someone explain how cacheing in browser works?
YSlow shows there is no Age Expires on my JS and graphics files. But
Firebug when I hit the page for 2nd and next times
shows that these files are cached and shows status 304 Not Modified.
I tried changing headers for specific files in IIS and it didn't change
what Firebug is showing. So are my files cached or not? |
|
|
| Back to top |
|
|
|
| 3P... |
| Posted: Fri Nov 06, 2009 9:30 pm |
|
|
|
Guest
|
Dnia 06-11-2009 o 08:34:24 Alexey Smirnov <alexey.smirnov at (no spam) gmail.com>
napisał(a):
Quote: On Nov 5, 8:47 pm, 3P <nos... at (no spam) serwer.pl> wrote:
Hi.
Can someone explain how cacheing in browser works?
YSlow shows there is no Age Expires on my JS and graphics files. But
Firebug when I hit the page for 2nd and next times
shows that these files are cached and shows status 304 Not Modified.
I tried changing headers for specific files in IIS and it didn't change
what Firebug is showing. So are my files cached or not?
So, maybe YSlow shows this wrong?
Firebug also doesn't show those headers. Maybe browsers cache all js and
graphics fils by default? |
|
|
| Back to top |
|
|
|
| 3P... |
| Posted: Sun Nov 08, 2009 7:00 am |
|
|
|
Guest
|
None of ASP.NET programmers interested in some caching of web application
elements? |
|
|
| Back to top |
|
|
|
|
