httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 61234] New: Add X-Forwarded-Proto to backend requests
Date Wed, 28 Jun 2017 22:26:26 GMT
https://bz.apache.org/bugzilla/show_bug.cgi?id=61234

            Bug ID: 61234
           Summary: Add X-Forwarded-Proto to backend requests
           Product: Apache httpd-2
           Version: 2.5-HEAD
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: mod_proxy
          Assignee: bugs@httpd.apache.org
          Reporter: bz.apache.org@chsc.dk
  Target Milestone: ---

Created attachment 35088
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=35088&action=edit
Add X-Forwarded-Proto

In order for backends behind a reverse proxy to reconstruct the original URL
requested by the client, mod_proxy needs to pass along not only the Host header
(in X-Forwarded-Host) but also the scheme.

With more and more websites adopting https, this is becoming increasingly
important.

The de-facto standard header for this purpose is X-Forwarded-Proto. Other
variants exist, but this seems to be the predominant name.

The header can be added manually with RequestHeader, but I think it should be
added automatically together with the other X-Forwarded-* headers when enabled.

The attached patch adds this feature. I am completely new to Apache httpd
development, so please help me get it right.

An alternative to adding support for X-Forwarded-Proto is to support the
Forwarded header specified in RFC 7239 (bug #58001). However, I believe both
solutions can coexist.

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message