Skip to content
This repository was archived by the owner on Apr 10, 2025. It is now read-only.
This repository was archived by the owner on Apr 10, 2025. It is now read-only.

Respect X-Forwarded-Proto #546

Closed
Closed
@GoogleCodeExporter

Description

@GoogleCodeExporter
We are running Apache server with mod_pagespeed in Amazon infrastructure behind 
Elastic Load Balancer. Load balancer handles also https requests so that they 
arrive to our Apache server as plain http. Apache thus sees all pages as plain 
http, and mod_pagespeed can also fetch all pages as http (or directly from 
server, this is not an issue). 

However, we have found no way of getting mod_pagespeed work with all urls in 
our setup. If trim_urls is on, pages served through https work correctly, but 
our service breaks in other parts (in some ajax content where html is pasted 
into page content). If trim_urls is off, all urls will have full path including 
domain and protocol part included (which in this case is http, despite load 
balancer receiving requests in https) inserted into them, so that the pages 
browsers receive through https include links to stylesheets and scripts with 
http as protocol - and browsers won't fetch these because of their security 
settings.

There seems to be no setting through which I could disable rewriting url 
domains and paths. What would solve the issue would be a setting which would 
simply enable us to tell mod_pagespeed to leave domain and path of each url as 
it is - in our case this would mean that they would always be relative to 
document root, but not specifying any protocol.

Or does anyone know any workaround to this issue?



Original issue reported on code.google.com by lari.loh...@gmail.com on 24 Oct 2012 at 10:26

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions