wppaste
WordPress

url_is_accessable_via_ssl( string $url ): bool

Since
2.5.0
Source
wp-includes/deprecated.php:3480
Determines if the URL can be accessed over SSL.

Description

Determines if the URL can be accessed over SSL by using the WordPress HTTP API to access the URL using https as the scheme.

Compatibility

Deprecated in WordPress 4.0.0. Kept for back-compatibility; avoid it in new code.

WordPress
since 2.5.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.

Parameters

$urlstring
The URL to test.

Return value

bool
Whether SSL access is available.

Performance profile

How much work a call to url_is_accessable_via_ssl() 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
Expensive

Reaches an outbound HTTP request via wp_remote_get().

Scaling
Constant

No loop in the body: the same number of instructions runs whatever you pass in.

Instructions
18–26

Executed per call on PHP 8.5, depending on the branch taken. The body compiles to 27.

Plugin surface
None

Nothing here hands control to plugin code.

Called by
0

Nothing in core calls this; the cost is only what you spend yourself.

What it touches

  • httpoutbound HTTP requestwp_remote_get()called directly
  • hookthird-party callbacksdo_action()one call below url_is_accessable_via_ssl()

Further down the call graph this can also reach query, option, cache, serialize 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 url_is_accessable_via_ssl() can have, taken from its control-flow graph on PHP 8.5.

WhenInstructionsCalls it makes
is_wp_error()18_deprecated_function(), set_url_scheme(), wp_remote_get(), is_wp_error()
!is_wp_error()24–26_deprecated_function(), set_url_scheme(), wp_remote_get(), is_wp_error(), wp_remote_retrieve_response_code()

Across PHP versions

Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 27 instructions, 18–26 executed per call, 3 branches. 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 · 5

Source code

View on Trac View on GitHub 

function url_is_accessable_via_ssl( $url ) {	_deprecated_function( __FUNCTION__, '4.0.0' ); 	$response = wp_remote_get( set_url_scheme( $url, 'https' ) ); 	if ( !is_wp_error( $response ) ) {		$status = wp_remote_retrieve_response_code( $response );		if ( 200 == $status || 401 == $status ) {			return true;		}	} 	return false;}

Changelog

Introduced in 2.5.0. Unchanged from 6.7.7 through 7.1.0.

  1. 6.7.7
  2. 6.8.8
  3. 6.9.7
  4. 7.0.4
  5. 7.1.0

Signature, return type and hooks compared across 5 parsed releases.

4.0.0
Deprecated.from the docblock
2.5.0
Introduced.from the docblock

About this page

Parsed data
Generated from the wordpress-develop 6.8.8 tag, from src/wp-includes/deprecated.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.