My favorites | Sign in
Project Home Wiki Issues Source
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 173: Rewrite resources when that moves them to a new domain
2 people starred this issue and may be notified of changes. Back to list
Status:  Fixed
Owner:  jmara...@google.com
Closed:  May 2011


Sign in to add a comment
 
Project Member Reported by jmaes...@google.com, Jan 3, 2011
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.
Feb 24, 2011
Project Member #1 sligocki@google.com
Josh, this was fixed recently, right?
Status: Fixed
Owner: jmara...@google.com
Labels: release-note
Feb 24, 2011
Project Member #2 jmaes...@google.com
I'm 98% sure it was.
Feb 28, 2011
Project Member #3 sligocki@google.com
It sounds like there's a little more to do on this. Add release-notes back and close this when it's ready.
Status: Started
Labels: -release-note
May 6, 2011
Project Member #4 jmara...@google.com
(No comment was entered for this change.)
Status: Fixed
Sign in to add a comment

Powered by Google Project Hosting