Skip to content
This repository was archived by the owner on Apr 10, 2025. It is now read-only.

Rewrite resources when that moves them to a new domain #173

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

Rewrite resources when that moves them to a new domain #173

GoogleCodeExporter opened this issue Apr 6, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

Right now, we only move resources in accordance with 
ModPagespeedMapRewriteDomain if those resources change in some way (rewritte, 
cache-extended).  In order to benefit from shifting resources to cookieless 
domains, we should consider always rewriting resources that are subject to this 
directive.  The simplest way would be as follows:

1) Add logic to DomainLawyer etc. to detect when a resource url can be 
rewritten in this way.
2) Modify cache extension so that it also rewrites these resources.

Original issue reported on code.google.com by [email protected] on 3 Jan 2011 at 3:18

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