Oh god, how did this get here i am not

I run a site and its main css file's pretty huge.
Looking through my server logs its being accessed the majority of times a page is reloaded.
Isn't this supposed to be stored in temporary internet history so it doesn't have to be reloaded?
Can I store it on the users computer so they only ever have to download it once?
Help me /prog/.


ExpiresActive On
<Files "*.css">
    ExpiresDefault A29030400
    Header append Cache-Control "public"
</Files>

>>2

HAHAHA nice try troll. 6/10

Seriously though...

The way modern browser like FireFox work, they need to download the CSS file each time the page is loaded to do standards compliant rendering.

Once would think a webmaster like yourself would know this basic thing.

Store it in cookies

Put it in cookies.jar

use pure html

store in cookies... strange idea...

if you use JS to load it, the page will be without at start, if you use php to load it, the client will need to redownload it each time.

One word, 304 Not Modified, thread over

>css
Stopped reading.

css
Stopped rendering.

> > > > css

Stopped leading.

XSL-FO
I enterprise'd.

How big is your CSS, are you like me who thinks like more than 10 lines of inline CSS is big?

Use PHP / ASP / whatever shit you are running to set these headers for requests to the CSS file:

Last-Modified: Mon, 16 Dec 2002 16:52:50 GMT
Expires: Tue, 17 Dec 2002 16:52:50 GMT
cache-Control: max-age=86400

Dates should be adjusted of course,
Last-Modified: Last modified time for file
Expires: A day from now should be plenty.
cache-Control: max-age=some number of seconds.

like this would almost certainly cause memory  leaks Just a  regular function that  takes two arguments  and returns the  bigger of the  blur functions you  might as well  be echo df.