[wp-trac] [WordPress Trac] #33626: wp_favicon_request() may set a bad value for Content-Length header

WordPress Trac noreply at wordpress.org
Tue Sep 1 01:29:19 UTC 2015


#33626: wp_favicon_request() may set a bad value for Content-Length header
--------------------------+------------------------------
 Reporter:  martiusweb    |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  3.0
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by dd32):

 Correct me if I'm wrong, but a BOM or other whitespace will cause other
 issues such as `headers already sent` errors? If that's the case, then
 accounting for it in the favicon request handler doesn't seem like it'd
 gain much anyway.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/33626#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list