[wp-trac] [WordPress Trac] #47288: The is_ssl() function will be not playing a part in using reverse proxy

[WordPress Trac]

#47288: The is_ssl() function will be not playing a part in using reverse proxy
--------------------------+------------------------
 Reporter:  rubycedar     |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Security      |     Version:  trunk
 Severity:  normal        |  Resolution:  duplicate
 Keywords:                |     Focuses:
--------------------------+------------------------
Changes (by SergeyBiryukov):

 * status:  new => closed
 * resolution:   => duplicate
 * component:  General => Security
 * milestone:  Awaiting Review =>


Comment:

 Duplicate of #31288.

 Hi @rubycedar, welcome to WordPress Trac!


 This is something that comes up often, but is not something that can be
 fixed due to the nature of handling client-provided headers, which is
 what's needed to address the issue.
 [https://core.trac.wordpress.org/ticket/31288#comment:17 See here for more
 info.]

 The long and short of it is that this is a server-level configuration
 issue with reverse proxy web servers. It's not a WordPress issue, and it's
 not limited to WordPress. There's no need to modify the `is_ssl()`
 function. You just need to add something along the lines of the following
 to your `wp-config.php` file:
 {{{
 $_SERVER['HTTPS'] = 1;
 }}}

 Any proxy configuration is "supported" by WordPress, you just need to
 remap the `$_SERVER['HTTPS']` server variable based the particular proxy
 configuration you're using.

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