Make WordPress Core

Opened 4 weeks ago

Closed 4 weeks ago

Last modified 4 weeks ago

#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's profile yanand Owned by:
Milestone: Priority: normal
Severity: normal Version: trunk
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.


4 weeks ago
#1

  • Keywords has-patch added

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

#2 follow-up: @joemcgill
4 weeks 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.

Last edited 4 weeks ago by joemcgill (previous) (diff)

#3 in reply to: ↑ 2 @yanand
4 weeks ago

Replying to joemcgill:Thanks for your replying.

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.