Storing "compiled" style-sheets in the cache is a good idea,
but letting the client to load a few files just increases the load on the server (why make 7 requests when you can make only 1?)
and +1 to VSE+!
When "Compiling" style-sheets, can we add an optimizer to remove unneeded characters? (white-spaces, etc..)
[RFC|Merged] No db storage of stylesheets and templates
Re: [RFC|Merged] No db storage of stylesheets and templates
Currently cache does not have any files that need to be served by the web server, and it is therefore possible to prevent web server from reading the cache directory. Putting assets in cache will also potentially expose other files in cache, e.g. the mail queue, to the web.
Re: [RFC|Merged] No db storage of stylesheets and templates
So make 2 cache directories, one with public access and the other with .htaccess or Web.config block (or outside install directory).Oleg wrote:Currently cache does not have any files that need to be served by the web server, and it is therefore possible to prevent web server from reading the cache directory. Putting assets in cache will also potentially expose other files in cache, e.g. the mail queue, to the web.
- callumacrae
- Former Team Member
- Posts: 1046
- Joined: Tue Apr 27, 2010 9:37 am
- Location: England
- Contact:
Re: [RFC|Merged] No db storage of stylesheets and templates
It would probably need to be morenaim wrote:So make 2 cache directories, one with public access and the other with .htaccess or Web.config block (or outside install directory).Oleg wrote:Currently cache does not have any files that need to be served by the web server, and it is therefore possible to prevent web server from reading the cache directory. Putting assets in cache will also potentially expose other files in cache, e.g. the mail queue, to the web.
assets/generated
than a cache-public
, in my opinion.