The extend cache filter is breaking my site. It appears to be replacing relative urls like /foo.js with absolute ones like http://foo.com/foo.js.pagespeed.jm.3C-n5JmHYZ.js. Unfortunately, my server is configured to only serve things over https, so all of these resources fail to serve. ModPageSpeed should realize that if the html page is served over https, the assets should be too, but it doesn't. How do I fix this?
That worked, thanks! Certain dynamic content was broken before (eg certain posts had the wrong destination) but that seems to have fixed it. It would be nice if this were default behavior though as you said. It might make sense to absolutify the paths if one more of the original paths were absolute, but when absolutely all of them are relative to the root they should be left alone.
--You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-di...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.