[wp-trac] [WordPress Trac] #14348: If it's a HEAD request, stop after the head!

WordPress Trac wp-trac at lists.automattic.com
Fri Mar 25 10:51:42 UTC 2011


#14348: If it's a HEAD request, stop after the head!
-----------------------------+------------------
 Reporter:  mitchoyoshitaka  |       Owner:
     Type:  enhancement      |      Status:  new
 Priority:  normal           |   Milestone:  3.2
Component:  Performance      |     Version:  3.0
 Severity:  normal           |  Resolution:
 Keywords:  has-patch close  |
-----------------------------+------------------
Changes (by hakre):

 * keywords:  has-patch => has-patch close


Comment:

 Replying to [comment:4 Denis-de-Bernardy]:
 > I can easily picture a plugin overriding headers after an output buffer
 gets started or something similar. The patch exits too early.

 True output buffers will flush on exit.

 >
 > I suspect anything short of output buffering, running the full WP, and
 discarding the output, will introduce potential issues. Alternatively we
 could close as wontfix or worksforme, since that would be what apache does
 already.

 Confirmed.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/14348#comment:14>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list