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

domain sharding & rewriting should apply to resources that are not cacheable. #264

Closed
GoogleCodeExporter opened this Issue Apr 6, 2015 · 3 comments

Comments

Projects
None yet
1 participant
@GoogleCodeExporter

GoogleCodeExporter commented Apr 6, 2015

Currently our domain-sharding & rewriting applies only to resources that have 
explicit public caching headers, or lack caching headers entirely.

This is certainly a requirement for mod_pagepseed to rewrite or cache-extend 
any resource, but we should be able to adjust the domains for uncacheable 
resources.

Original issue reported on code.google.com by jmara...@google.com on 10 Apr 2011 at 5:35

@GoogleCodeExporter

This comment has been minimized.

GoogleCodeExporter commented Apr 6, 2015

Original comment by jmara...@google.com on 10 Apr 2011 at 5:36

@GoogleCodeExporter

This comment has been minimized.

GoogleCodeExporter commented Apr 6, 2015

That this issue also applies to resources that don't have an associated filter. 
 E.g. if a site has rewrite_images and extend_cache disabled, then no images 
will be sharded.

Original comment by jmara...@google.com on 26 Apr 2011 at 8:28

@GoogleCodeExporter

This comment has been minimized.

GoogleCodeExporter commented Apr 6, 2015

This is fixed now with a new filter:  rewrite_domains.  The filter is not (yet) 
in the core set; it must be enabled with ModPagespeedEnableFilters.

Original comment by jmara...@google.com on 6 May 2011 at 3:27

  • Changed state: Fixed
  • Added labels: release-note
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment