WordPress.org

Make WordPress Core

Opened 3 years ago

Closed 3 years ago

Last modified 2 years ago

#20567 closed enhancement (duplicate)

is_ssl check for proxy forwarding

Reported by: Mvied Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.4
Component: General Keywords: has-patch
Focuses: Cc:

Description

When using SSL in a proxy environment, sometimes the proxy is configured to set the X-Forwarded headers rather than modify the original response headers. This patch adds two additional conditionals to is_ssl to check for these X-Forwarded headers.

Attachments (1)

functions.php.patch (593 bytes) - added by Mvied 3 years ago.
/wp-includes/functions.php

Download all attachments as: .zip

Change History (6)

@Mvied3 years ago

/wp-includes/functions.php

comment:2 @SergeyBiryukov3 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to duplicate
  • Status changed from new to closed

Actually, a duplicate of #15733.

comment:3 @Mvied3 years ago

The other ticket's patch only checks HTTP_X_FORWARDED_PROTO and not HTTP_X_FORWARDED_PORT. Should I upload a patch to the other ticket?

comment:4 @nacin3 years ago

Based on the comments in #15733, this is not a WordPress configuration issue. Set $_SERVER['HTTPS'] to whatever it is supposed to be on your environment via wp-config.php.

comment:5 @webaware2 years ago

There's a simple plugin in Gist that could easily be modified to work with whichever situation you have on your specific server. Maybe someone could turn it into a configurable plugin if they felt the urge :)

Explanation of Gist in this blog post

Version 0, edited 2 years ago by webaware (next)
Note: See TracTickets for help on using tickets.