wppaste
WordPress

WP_Http_Cookie::getHeaderValue(): string

Since
2.8.0
Source
wp-includes/class-wp-http-cookie.php:230
Convert cookie name and value back to header string.

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.

Return value

string
Header encoded cookie name and value.

Performance profile

How much work a call to WP_Http_Cookie::getHeaderValue() 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
3–17

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

Plugin surface
1 hook

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

Called by
1

1 place in core call this, so the cost is paid more often than your own code shows.

What it touches

  • hookthird-party callbacksapply_filters()called directly

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_Http_Cookie::getHeaderValue() can have, taken from its control-flow graph on PHP 8.5.

WhenInstructionsCalls it makes
!isset($value)3–5none
isset($value)17apply_filters()

Across PHP versions

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

Hooks and filters fired · 1

One hook fires while WP_Http_Cookie::getHeaderValue() runs, in this order:

  1. apply_filters( wp_http_cookie_value )filterline 243 (+13 into the body)

    Filters the header-encoded cookie value.

Uses · 1

  • apply_filters()Calls the callback functions that have been added to a filter hook.

Used by · 1

Source code

	public function getHeaderValue() { // phpcs:ignore WordPress.NamingConventions.ValidFunctionName.MethodNameInvalid		if ( ! isset( $this->name ) || ! isset( $this->value ) ) {			return '';		} 		/**		 * Filters the header-encoded cookie value.		 *		 * @since 3.4.0		 *		 * @param string $value The cookie value.		 * @param string $name  The cookie name.		 */		return $this->name . '=' . apply_filters( 'wp_http_cookie_value', $this->value, $this->name );	}

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.7.7 tag, from src/wp-includes/class-wp-http-cookie.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.