[wp-trac] [WordPress Trac] #33626: wp_favicon_request() may set a bad value for Content-Length header
WordPress Trac
noreply at wordpress.org
Mon Sep 7 02:17:35 UTC 2015
#33626: wp_favicon_request() may set a bad value for Content-Length header
------------------------------------+---------------------
Reporter: martiusweb | Owner: dd32
Type: defect (bug) | Status: closed
Priority: normal | Milestone: 4.4
Component: General | Version: 3.0
Severity: normal | Resolution: fixed
Keywords: has-patch dev-feedback | Focuses:
------------------------------------+---------------------
Changes (by dd32):
* owner: => dd32
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"33935"]:
{{{
#!CommitTicketReference repository="" revision="33935"
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
}}}
--
Ticket URL: <https://core.trac.wordpress.org/ticket/33626#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list