Fires once the requested HTTP headers for caching, content type, etc. have been sent.
Parameters
$wp
WP- Current WordPress environment instance (passed by reference).
Source
do_action_ref_array( 'send_headers', array( &$this ) );
Changelog
Version | Description |
---|---|
2.1.0 | Introduced. |
Since WordPress 6.1, the send_headers action has been moved to later in core load. It is now triggered after pre_get_posts.
Conditionals tags can now be used (is_single, is_404 and so on).
More information on this dev-note: https://make.wordpress.org/core/2022/10/10/moving-the-send_headers-action-to-later-in-the-load/
As an example: HTML5 Boilerplate provides an X-UA-Compatible meta element by default. This element breaks validation but can be moved to a header. Adding the following to functions.php fixes the validation issue and provides IE users a better experience.
Example migrated from Codex:
As an example: HTML5 Boilerplate provides an X-UA-Compatible meta element by default. This element breaks validation, but can be moved to a header. Adding the following to functions.php fixes the validation issue and provides IE users a better experience.
Example of how to conditionally send a header, replacing previously set header, if any…