Your file will probably be cached - but it depends ...
Different browsers have slightly different types of behavior - most noticeably when working with ambiguous / restricted caching headers coming from the server. If you send a clear signal, browsers obey almost all the time.
The biggest variance is the default caching configuration for different web servers and application servers.
Some (like Apache) are more likely to serve known static file types with HTTP headers, encouraging the browser to cache them, while other servers can send no-cache commands with each response, regardless of file type.
...
So first, read some of the excellent HTTP caching . HTTP caching and caching for Content Publishers was a real discovery for me :-)
Then install and script Firebug and Live HTTP Headers to see which headers your server actually sends.
Then read your web server docs to find out how to configure them to perfection (or talk with your administrator to do this for you).
...
As for what happens when the browser restarts, it depends on the browser and user configuration.
Generally, expect the browser to be more likely to log into the server after each restart to see if something has changed (see If-Last-Modified and If-None-Match ).
If you configured your server correctly, it will have to return a super-short 304 Not Modified (with very low bandwidth) and after that the browser will use the cache as usual.
Már Örlygsson Jan 20 '09 at 8:32 2009-01-20 08:32
source share