search

crowell / modpagespeed_tmp

Automatically exported from code.google.com/p/modpagespeed
Apache License 2.0
0 stars 0 forks source link

When the Serf fetcher attempts to get a resource that is HTTPS, when fetching over HTTP, it should send '--header 'x-forwarded-proto: https'' #724

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Try optimize an HTTPS resource only available over HTTPS through a reverse 
proxy

What is the expected output? What do you see instead?
There are some sites who require you fetch resources only over HTTPS because 
they decided to implement some backwards redirect policy for protocol 
correction.

What version of the product are you using (please check X-Mod-Pagespeed
header)?
1.3.25.4

On what operating system?
Ubuntu10.04

Which version of Apache?
2.2.2

Which MPM?
Event

URL of broken page:
Resources cannot be fetched so the page just renders as is.

Original issue reported on code.google.com by hayes...@gmail.com on 20 Jun 2013 at 12:30

GoogleCodeExporter commented 9 years ago 
Maks -- what's your feeling about x-forwarded-for?  Is there any downside risk 
to adding this unconditionally?

https://en.wikipedia.org/wiki/List_of_HTTP_header_fields

Original comment by jmara...@google.com on 25 Jun 2013 at 2:40

GoogleCodeExporter commented 9 years ago 
Did you mean "x-forwarded-proto" or "x-forwarded-for"?

Original comment by hayes...@gmail.com on 25 Jun 2013 at 4:58

GoogleCodeExporter commented 9 years ago 
Hey all,

I think here is the same issue. 

https://github.com/pagespeed/ngx_pagespeed/issues/830

Still doesn't work and can't debug, because I can't find the way of how to 
print something in error_log.. Who can help me?

D.

Original comment by donatas....@gmail.com on 18 Oct 2014 at 1:05