Favicon: Do not specify a Content-Length: 0 header for our "empty" response to fail more gracefully on environments with extra whitespace on output.

This allows for the web server to generate the appropriate `Content-Length` header for the request, allowing for strict clients/proxies/servers to process the response.

Props swissspidy.
Fixes #33626

Built from https://develop.svn.wordpress.org/trunk@33935


git-svn-id: http://core.svn.wordpress.org/trunk@33904 1a063a9b-81f0-0310-95a4-ce76da25c4cd
This commit is contained in:
Dion Hulse 2015-09-07 02:18:26 +00:00
parent a3f82f92f1
commit 36bda54e88
2 changed files with 1 additions and 2 deletions

View File

@ -132,7 +132,6 @@ function wp_check_php_mysql_versions() {
function wp_favicon_request() { function wp_favicon_request() {
if ( '/favicon.ico' == $_SERVER['REQUEST_URI'] ) { if ( '/favicon.ico' == $_SERVER['REQUEST_URI'] ) {
header('Content-Type: image/vnd.microsoft.icon'); header('Content-Type: image/vnd.microsoft.icon');
header('Content-Length: 0');
exit; exit;
} }
} }

View File

@ -4,7 +4,7 @@
* *
* @global string $wp_version * @global string $wp_version
*/ */
$wp_version = '4.4-alpha-33934'; $wp_version = '4.4-alpha-33935';
/** /**
* Holds the WordPress DB revision, increments when changes are made to the WordPress DB schema. * Holds the WordPress DB revision, increments when changes are made to the WordPress DB schema.