wp_is_https_supported(): bool
- Since
- 5.7.0
- Source
wp-includes/https-detection.php:70
Compatibility
- WordPress
- since 5.7.0
- PHP
- 7.4–8.6-dev
- 6.7.7
- 6.8.8
- 6.9.7
- 7.0.4
- 7.1.0
Present in every tracked release (6.7.7 to 7.1.0), and compiles on PHP 7.4 through 8.6-dev.
Return value
bool- True if HTTPS is supported, false otherwise.
Performance profile
How much work a call to wp_is_https_supported() does, and what it touches: the algorithmic scaling, the Zend instruction count per call across PHP versions, the hooks it hands control to, and the core code that calls it. Measured from the compiled opcodes, not a stopwatch, so every number is identical on any machine running the same PHP version, and every function in core is ranked by cost.
- Cost class
- Moderate
- Scaling
- Constant
- Instructions
- 8–14
- Plugin surface
- None
- Called by
- 1
Reads stored settings via get_option(), cached per request but not free on a cold cache.
No loop in the body: the same number of instructions runs whatever you pass in.
Executed per call on PHP 8.5, depending on the branch taken. The body compiles to 14.
Nothing here hands control to plugin code.
1 place in core call this, so the cost is paid more often than your own code shows.
What it touches
- optionoption read or write
get_option()called directly - hookthird-party callbacks
apply_filters()one call below wp_is_https_supported() - cacheobject cache
wp_cache_get()one call below wp_is_https_supported() - serializeserialisation
maybe_unserialize()one call below wp_is_https_supported()
Further down the call graph this can also reach http, query and transient. Those are the worst case, several calls deep and usually down an error path, not what a normal call pays.
What one call costs · 2 distinct outcomes
One number would be a lie: the work depends on which branch runs. These are every distinct cost wp_is_https_supported() can have, taken from its control-flow graph on PHP 8.5.
| When | Instructions | Calls it makes |
|---|---|---|
$https_detection_errors !== false | 8 | get_option() |
$https_detection_errors === false | 14 | get_option(), wp_update_https_detection_errors(), get_option() |
Across PHP versions
Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 14 instructions, 8–14 executed per call, 1 branch. The work does not change between versions.
An instruction is not a fixed amount of time, so a matching count is not necessarily the same speed; what it rules out is a difference in the work itself.
Uses · 2
- get_option()Retrieves an option value based on an option name.
- wp_update_https_detection_errors()Runs a remote HTTPS request to detect whether HTTPS supported, and stores potential errors.
Used by · 1
- WP_Site_Health::get_test_https_status()Tests if the site is serving content over HTTPS.
Source code
function wp_is_https_supported() { $https_detection_errors = get_option( 'https_detection_errors' ); // If option has never been set by the Cron hook before, run it on-the-fly as fallback. if ( false === $https_detection_errors ) { wp_update_https_detection_errors(); $https_detection_errors = get_option( 'https_detection_errors' ); } // If there are no detection errors, HTTPS is supported. return empty( $https_detection_errors );}Changelog
Introduced in 5.7.0. Unchanged from 6.7.7 through 7.1.0.
Signature, return type and hooks compared across 5 parsed releases.
About this page
- Parsed data
- Generated from the wordpress-develop 6.7.7 tag, from
src/wp-includes/https-detection.php, and regenerated for each WordPress release so it tracks the code rather than a snapshot of it. - Corrections
- Something wrong on this page? Report it and it gets fixed in the next regeneration.