[wp-trac] [WordPress Trac] #14348: If it's a HEAD request, stop after the head!
WordPress Trac
wp-trac at lists.automattic.com
Thu Jul 22 02:46:17 UTC 2010
#14348: If it's a HEAD request, stop after the head!
-----------------------------+----------------------------------------------
Reporter: mitchoyoshitaka | Owner:
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Performance | Version: 3.0
Severity: normal | Keywords: has-patch
-----------------------------+----------------------------------------------
Changes (by mitchoyoshitaka):
* cc: mitchoyoshitaka (added)
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.
I updated the patch to include a boolean filter, exit_on_http_head, so
that plugins can turn this mechanism off if there is a problem.
If I were a betting man, I would bet that, out of the plugins which output
a HTTP header, the subset which particularly care about the integrity of
that header when it's a HEAD request, not just when it's a GET or POST, is
very small.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/14348#comment:10>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list