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

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

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

Comments

@GoogleCodeExporter
Copy link

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
Copy link
Author

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

@GoogleCodeExporter
Copy link
Author

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
Copy link
Author

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 subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant