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 |
|---|---|
| 877 | * @uses apply_filters() Calls 'wp_redirect' hook on $location and $status. |
| 878 | * |
| 879 | * @param string $location The path to redirect to |
| 880 | * @param int $status Status code to use |
| 881 | * @return bool False if $location is not set |
| 882 | */ |
| 883 | function wp_redirect($location, $status = 302) { |
| 884 | global $is_IIS; |
| 885 | |
| 886 | $location = apply_filters('wp_redirect', $location, $status); |
| 887 | $status = apply_filters('wp_redirect_status', $status, $location); |
| 888 | |
| 889 | if ( !$location ) // allows the wp_redirect filter to cancel a redirect |
| 890 | return false; |
| 891 | |
| 892 | $location = wp_sanitize_redirect($location); |
| 893 | |
| 894 | if ( !$is_IIS && php_sapi_name() != 'cgi-fcgi' ) |
| 895 | status_header($status); // This causes problems on IIS and some FastCGI setups |