#39659 closed enhancement (duplicate)
Offloaded SSL Detection
Reported by: | miraclebg | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | General | Keywords: | |
Focuses: | Cc: |
Description
Currently Wordpress supports detection only by checking the HTTPS environment variable (on,1).
I would suggest also adding forwarded protocol headers - like ones coming from a SSL offloader (HaProxy for example) which would normally send in this case:
HTTP_X_FORWARDED_PROTO=https
It is currently impossible to do this otherwise unless manually editing the WordPress core.
I am attaching a screenshot of the proposed change i have to do every time manually.
Thank you!
Attachments (1)
Change History (3)
#1
@
8 years ago
- Component changed from HTTP API to General
- Milestone Awaiting Review deleted
- Resolution set to duplicate
- Status changed from new to closed
Hello miraclebg, welcome to Trac!
Thanks for your report, it's something that comes up often:
- #15733
- WordPress Installation behind reverse-proxy ssl redirect loop
- #19654
- Allow overload of is_ssl() via a filter
- #25222
- Detect https correctly when behind a proxy/loadbalancer
- #31288
- IS_SSL should check return true for SSL Terminated load balancing
- #31439
- is_ssl not compatible with server - option for filter or hook
- #32354
- is_ssl() does not work on cloud hosting
- #33730
- ssl is not detecting for cloudflare
- #34298
- Amazon LB SSL / HTTP_X_FORWARDED_PROTO
- #34912
- wp-admin/load-styles.php not serving multiple assets over HTTPS
- #39659
- Offloaded SSL Detection
- #40710
- Improvement ssl detection
- #57125
- custom changes to wp-includes/functions.php overwritten by automatic upgrades, breaking Cloudflare or squid frontend
Please take a look at #31288 which provides information on how to solve this for your environment.
Note: See
TracTickets for help on using
tickets.
Proposed fix