Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow explicit control over CSS concat etc #76

Closed
GoogleCodeExporter opened this issue Apr 6, 2015 · 2 comments
Closed

Allow explicit control over CSS concat etc #76

GoogleCodeExporter opened this issue Apr 6, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

@GoogleCodeExporter GoogleCodeExporter commented Apr 6, 2015

I would want htaccess control over which css or js are concatenated, and which 
are left as separate files. The reason for this is that often your home page 
will begin with 13 js files = 450kb, but the about us page will have 14 js 
files = 451kb, so for one extra 1kb file the server reconcatenates, reminifies, 
rezips and resends all the original 13 files + 1 that are already in the 
browser cache.

Original issue reported on code.google.com by jmara...@google.com on 12 Nov 2010 at 6:48

@GoogleCodeExporter
Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Apr 6, 2015

This was from "wally" on 
http://m.blogs.sitepoint.com/2010/11/08/optimization-made-easy-with-mod_pagespee
d/

Original comment by jmara...@google.com on 12 Nov 2010 at 6:51

@GoogleCodeExporter
Copy link
Author

@GoogleCodeExporter GoogleCodeExporter commented Apr 6, 2015

This is now supported (in SVN) with

ModPagespeedDisallow wildcard_spec

This is also described in the FAQ (although the example there talks about 
avoiding the rewriting of */jquery.js, the remedy is the same).

Original comment by jmara...@google.com on 3 Dec 2010 at 10:42

  • Changed state: Fixed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.