Rewrite resources when that moves them to a new domain

[GoogleCodeExporter]

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 jmaes...@google.com on 3 Jan 2011 at 3:18

[GoogleCodeExporter]

Josh, this was fixed recently, right?

Original comment by sligocki@google.com on 24 Feb 2011 at 10:40

• Changed state: Fixed
• Added labels: release-note

[GoogleCodeExporter]

I'm 98% sure it was.

Original comment by jmaes...@google.com on 24 Feb 2011 at 10:55

[GoogleCodeExporter]

It sounds like there's a little more to do on this. Add release-notes back and 
close this when it's ready.

Original comment by sligocki@google.com on 28 Feb 2011 at 7:19

• Changed state: Started
• Removed labels: release-note

[GoogleCodeExporter]

Original comment by jmara...@google.com on 6 May 2011 at 5:20

• Changed state: Fixed