[wp-trac] [WordPress Trac] #15733: WordPress Installation behind reverse-proxy ssl redirect loop

[WordPress Trac]

#15733: WordPress Installation behind reverse-proxy ssl redirect loop
--------------------------------------------+----------------------
 Reporter:  costasd                         |       Owner:  (none)
     Type:  defect (bug)                    |      Status:  closed
 Priority:  normal                          |   Milestone:
Component:  General                         |     Version:  3.0.2
 Severity:  minor                           |  Resolution:  wontfix
 Keywords:  ssl nginx apache reverse-proxy  |     Focuses:
--------------------------------------------+----------------------

Comment (by xani666):

 @jorbin You got 8 years of proof lack of handling of x-forwarded for is
 causing problem, right in this ticket, just look at amount of duplicates
 merged. Or just google it. Or just look at the docs of the one of most
 used LB services:

 https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/x
 -forwarded-headers.html

 or LB daemons

 https://cbonte.github.io/haproxy-
 dconv/1.7/configuration.html#option%20forwardfor

 And what exact RFC "set HTTPS header to on" is in, because I can't find
 any yet it is still what WP relies on. So please, stop with the "hurr durr
 it is not in official OFFICIAL official standard" because that's not how
 internet is built.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/15733#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform