You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 21, 2023. It is now read-only.
A user that has mod_pagespeed running behind a proxy may have a situation where
mod_pagespeed thinks its rewriting HTML being served on HTTPS. However a proxy
in front of mod_pagespeed serves it as HTTPS. We can get the resources
rewritten properly with ModPagespeedMapRewriteDomain, however,
add_instrumentation will still send beacons via http.
I think this is a matter of doing that mapping in add_instrumentation_filter.cc.
Original issue reported on code.google.com by jmara...@google.com on 13 Jul 2012 at 7:06
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
jmara...@google.com
on 13 Jul 2012 at 7:06The text was updated successfully, but these errors were encountered: