Pagespeed filters failed

[JJ]

I came across a site where all the pagespeed filters failed except
domain sharding while testing using apache proxy. The site is www.chiliad.com
. Any idea why none of the filters worked ?

[Joshua Marantz]

Can you try adding this to your pagespeed.conf:

    ModPagespeedDomains chiliad.com

The reason you need this is that mod_pagespeed will by default rewrite resources on the same domain as the HTML file, which in this case is www.chiliad.com.  But all your resources are on chiliad.com.

You could also write:

    ModPagespeedDomain *chiliad.com 

or more generally (if you are trying to create an open proxy in an intranet):

    ModPagespeedDomain *

Just don't do that on the open internet for security reasons.

-Josh

[Jimy Johny]

Thanks for the suggestion.

How did you find that all the resources is from chiliad.com. When I checked the source code and the requests, except 3 links, all others are coming from www.chiliad.com.

However, I tried ModPagespeedDomain *.chiliad.com , but it didn't worked.

JJ

[Joshua Marantz]

I looked on Firebug, but I made a mistake -- it just gave the top-level domain.

The reason mod_pagespeed doesn't rewrite resources on this site is the "Vary:*" header returned with each of your resources.   Do you know why that header is there?

That's used as a signal by the underlying PageSpeed Insights libraries to indicate that this resource can change for all kinds of different reasons.  Looking at Firebug, I see that Firefox does not cache these resources, so mod_pagespeed is consistent with Firefox.

If mod_pagespeed can't cache a resource, then it won't try to optimize it, because it'd have to re-optimize it on every refresh.

If you can remove the "Vary:*" from your Apache configuration mod_pagespeed should optimize your resources.

-Josh

[Jimy Johny]

Thanks. That fixed the issue.

JJ