#61463 closed defect (bug) (duplicate)
The "is_ssl()" function fails to get the correct protocol when WordPress is deployed on an upstream server.
Reported by: | yanand | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 6.6 |
Component: | General | Keywords: | dev-feedback |
Focuses: | coding-standards, php-compatibility | Cc: |
Description
When WordPress is deployed on an upstream server with its port set to 80, and the upstream server (such as Nginx) handles HTTPS requests on port 443, the is_ssl() function in WordPress may malfunction, leading to UI issues where some resources stop to load.
Change History (3)
This ticket was mentioned in PR #6853 on WordPress/wordpress-develop by yananhub.
6 months ago
#1
- Keywords has-patch added
#2
follow-up:
↓ 3
@
6 months ago
- Keywords has-patch removed
- Milestone Awaiting Review deleted
- Resolution set to duplicate
- Status changed from new to closed
Hi @yanand, and welcome to Trac! This issue has previously been come up in #31288. This comment provides more context about why this has not been addressed.
Note: See
TracTickets for help on using
tickets.
When WordPress is deployed on an upstream server with its port set to 80, and the upstream server (such as Nginx) handles HTTPS requests on port 443, the is_ssl() function in WordPress may malfunction, leading to UI issues where some resources stop to load.
Trac ticket: https://core.trac.wordpress.org/ticket/61463