If it's a HEAD request, stop after the head!
|Reported by:||mitchoyoshitaka||Owned by:||markjaquith|
|Severity:||normal||Keywords:||has-patch 3.5-early needs-unit-tests commit|
|Cc:||mitchoyoshitaka, aaron@…, mbijon, solaris.smoke@…, neo@…, sirzooro, kpayne@…|
Right now, as far as I can tell, when a HTTP HEAD request is made against WordPress, we go ahead and produce the entire page content, only to have it ignored. Attached is a patch to repair this.
While not a huge issue, if you happen to receive lots of HEAD requests, this can make a large difference, as each HEAD request will be much faster and not waste precious resources.
I have tried to ensure that this patch, by being in send_headers, will produce a HEAD response functionally identical to the response header of GET/POST requests, as it should be.
Change History (60)
comment:11 nacin — 3 years ago
- Keywords 3.2-early added
- Milestone changed from Awaiting Review to Future Release
- Type changed from defect (bug) to enhancement
comment:12 scribu — 2 years ago
- Keywords 3.2-early removed
- Milestone changed from Future Release to 3.2
comment:19 koopersmith — 2 years ago
- Keywords 3.3-early added; close removed
- Milestone changed from Future Release to 3.3
comment:21 mbijon — 21 months ago
- Keywords 2nd-opinion added
comment:25 ryan — 20 months ago
- Keywords 3.4-early added; 3.3-early removed
- Milestone changed from 3.3 to Future Release
comment:28 nacin — 15 months ago
- Keywords 3.5-early added; 3.4-early removed
- Milestone changed from 3.4 to Future Release
comment:35 in reply to: ↑ 34 kurtpayne — 10 months ago
comment:39 in reply to: ↑ 38 ; follow-ups: ↓ 40 ↓ 43 mitchoyoshitaka — 10 months ago
comment:50 markjaquith — 8 months ago
- Resolution set to fixed
- Status changed from accepted to closed