Skip to content
This repository has been archived by the owner on Apr 21, 2023. It is now read-only.

CSS files not rewritten 100% of the time #666

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

CSS files not rewritten 100% of the time #666

GoogleCodeExporter opened this issue Apr 6, 2015 · 4 comments
Labels
auto-migrated Priority-Medium Type-Defect

Comments

@GoogleCodeExporter
Copy link 

What steps will reproduce the problem?
1. Checking page with filters in .conf file.
2. Checking page with filters by query parameter...
3. The problem is that I've got more points on Google PageSpeed Insights when 
I've turn the same filters by query parameter.

What is the expected output? What do you see instead?
I don't know why, but I've got more points on Google PageSpeed Insights when I 
check my website with filters enabled by putting them in query parameter. Why 
it is done? And the second questions is, why one of my .css file isn't rewrited 
when the other are (that one .css is in other folder, but it should be rewrited 
too, shouldn't it?)?

What version of the product are you using (please check X-Mod-Pagespeed
header)?
1.2.24.1-2581

On what operating system?
Debian 6 Squeeze

Which version of Apache?
2.4

Original issue reported on code.google.com by foctr...@gmail.com on 7 Apr 2013 at 10:21
@GoogleCodeExporter
Copy link
Author 

I wonder if this may be linked to issue 667 - ie. some of your filters are 
actually enabled by default, but the line:

    ModPagespeedEnableFilters xxx

is actually then disabling filter xxx !!

Original comment by rwap.services on 8 Apr 2013 at 9:08

@GoogleCodeExporter
Copy link
Author 

Per comments in Issue 667, ModPagespeedEnableFilters is not supposed to toggle, 
and we haven't seen any evidence yet suggesting that it does.

Could it be something in your pagespeed.conf or .htaccess files that's causing 
filters to be disabled you are not expecting?

Also, note that mod_pagespeed optimizes resources in the background, and stores 
them in the cache.  For short-expiring resources on not-frequently-accessed 
pages (e.g. debug or staging servers) you may have to refresh a few times to 
see optimized results.

Original comment by jmara...@google.com on 8 Apr 2013 at 1:29

@GoogleCodeExporter
Copy link
Author 

Summary was: Pagespeed isn't working correctly.

Original comment by jmara...@google.com on 8 Apr 2013 at 1:30

  • Changed title: CSS files not rewritten 100% of the time
  • Changed state: RequestClarification

@GoogleCodeExporter
Copy link
Author

Original comment by sligocki@google.com on 29 Oct 2014 at 7:50

  • Changed state: Closed

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
auto-migrated Priority-Medium Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter