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

[WordPress Trac]

#14348: If it's a HEAD request, stop after the head!
---------------------------------------------+------------------
 Reporter:  mitchoyoshitaka                  |       Owner:
     Type:  enhancement                      |      Status:  new
 Priority:  normal                           |   Milestone:  3.5
Component:  Performance                      |     Version:  3.0
 Severity:  normal                           |  Resolution:
 Keywords:  has-patch 3.5-early 2nd-opinion  |
---------------------------------------------+------------------

Comment (by mbijon):

 I just tested attachment:14348-7.diff with Fiddler & the test suite. Both
 ways it worked as expected.

 The {{{do_action()}}} is in the correct place, it's executed at the same
 point as in my previous attachment:14348-6.diff. The distribution of code
 makes this a bit spaghetti'ish but shouldn't have any negative effects.

 Putting spaghetti aside, the action does seem like it's unnecessary. Such
 an abstraction is a positive thing for code that might be run in multiple
 places, but I can't think of any reasons to call
 {{{handle_head_request()}}} from a plugin that wouldn't already be
 addressed by the {{{exit_on_http_head}}} filter & Kurt's added
 {{{wp_die_handler}}}. Anyone else?

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