WP hooks navigation: Home/browse • Actions index • Filters index
To save our bandwidth, we show only a snippet of code around each occurence of the hook. View complete file in SVN (without highlighting).
The best way to understand what a hook does is to look at where it occurs in the source code.
do_action( "hook_name" )apply_filters( "hook_name", "what_to_filter" ).Remember, this hook may occur in more than one file. Moreover, the hook's context may change from version to version.
| Line | Code |
|---|---|
| 348 | * The allowed headers are passed to the browser to specify which |
| 349 | * headers can be passed to the REST API. By default, we allow the |
| 350 | * Content-* headers needed to upload files to the media endpoints. |
| 351 | * As well as the Authorization and Nonce headers for allowing authentication. |
| 352 | * |
| 353 | * @since 5.5.0 |
| 354 | * |
| 355 | * @param string[] $allow_headers The list of request headers to allow. |
| 356 | */ |
| 357 | $allow_headers = apply_filters( 'rest_allowed_cors_headers', $allow_headers ); |
| 358 | |
| 359 | $this->send_header( 'Access-Control-Allow-Headers', implode( ', ', $allow_headers ) ); |
| 360 | |
| 361 | /** |
| 362 | * Filters whether to send nocache headers on a REST API request. |
| 363 | * |
| 364 | * @since 4.4.0 |
| 365 | * |
| 366 | * @param bool $rest_send_nocache_headers Whether to send no-cache headers. |