#47288 closed defect (bug) (duplicate)
The is_ssl() function will be not playing a part in using reverse proxy
| Reported by: | rubycedar | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Security | Version: | 5.3 |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
Description
The is_ssl() function will be not playing a part in using reverse proxy.
Attachments (1)
Change History (3)
Note:
See TracTickets
for help on using tickets.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Duplicate of #31288.
Hi @rubycedar, welcome to WordPress Trac! Thanks for the report.
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. 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 yourwp-config.phpfile: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.