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 |
---|---|
320 | * The allowed headers are passed to the browser to specify which |
321 | * headers can be passed to the REST API. By default, we allow the |
322 | * Content-* headers needed to upload files to the media endpoints. |
323 | * As well as the Authorization and Nonce headers for allowing authentication. |
324 | * |
325 | * @since 5.5.0 |
326 | * |
327 | * @param string[] $allow_headers The list of request headers to allow. |
328 | */ |
329 | $allow_headers = apply_filters( 'rest_allowed_cors_headers', $allow_headers ); |
330 |
|
331 | $this->send_header( 'Access-Control-Allow-Headers', implode( ', ', $allow_headers ) ); |
332 |
|
333 | /** |
334 | * Filters whether to send nocache headers on a REST API request. |
335 | * |
336 | * @since 4.4.0 |
337 | * |
338 | * @param bool $rest_send_nocache_headers Whether to send no-cache headers. |