wppaste
WordPress

WP_Http_Encoding::accept_encoding( string $url, array $args ): string

Since
2.8.0
Source
wp-includes/class-wp-http-encoding.php:149
What encoding types to accept and their priority values.

Compatibility

WordPress
since 2.8.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
$argsarray

Return value

string
Types of encoding to accept.

Performance profile

How much work a call to WP_Http_Encoding::accept_encoding() 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
Trivial

Touches nothing outside its own arguments.

Scaling
Constant

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

Instructions
20–24

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

Plugin surface
1 hook

Third-party callbacks on 'wp_http_accept_encoding' run inside this call, and their cost is not bounded by anything here.

Called by
0

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

What it touches

  • hookthird-party callbacksapply_filters()called directly

What one call costs · 1 distinct outcome

One number would be a lie: the work depends on which branch runs. These are every distinct cost WP_Http_Encoding::accept_encoding() can have, taken from its control-flow graph on PHP 8.5.

WhenInstructionsCalls it makes
always20–24::is_available(), apply_filters()

Across PHP versions

PHPCompiledExecutedBranchesNotes
8.6-dev2820–244
8.52820–244
8.42820–2443 fewer instructions than PHP 8.3
8.33123–274
8.23123–274
8.13123–274
7.43123–274

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.

Hooks and filters fired · 1

One hook fires while WP_Http_Encoding::accept_encoding() runs, in this order:

  1. apply_filters( wp_http_accept_encoding )filterline 184 (+35 into the body)

    Filters the allowed encoding types.

Uses · 2

Source code

	public static function accept_encoding( $url, $args ) {		$type                = array();		$compression_enabled = self::is_available(); 		if ( ! $args['decompress'] ) { // Decompression specifically disabled.			$compression_enabled = false;		} elseif ( $args['stream'] ) { // Disable when streaming to file.			$compression_enabled = false;		} elseif ( isset( $args['limit_response_size'] ) ) { // If only partial content is being requested, we won't be able to decompress it.			$compression_enabled = false;		} 		if ( $compression_enabled ) {			if ( function_exists( 'gzinflate' ) ) {				$type[] = 'deflate;q=1.0';			} 			if ( function_exists( 'gzuncompress' ) ) {				$type[] = 'compress;q=0.5';			} 			if ( function_exists( 'gzdecode' ) ) {				$type[] = 'gzip;q=0.5';			}		} 		/**		 * Filters the allowed encoding types.		 *		 * @since 3.6.0		 *		 * @param string[] $type Array of what encoding types to accept and their priority values.		 * @param string   $url  URL of the HTTP request.		 * @param array    $args HTTP request arguments.		 */		$type = apply_filters( 'wp_http_accept_encoding', $type, $url, $args ); 		return implode( ', ', $type );	}

Changelog

Introduced in 2.8.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.

About this page

Parsed data
Generated from the wordpress-develop 6.9.7 tag, from src/wp-includes/class-wp-http-encoding.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.