ACTION-710: Test the Effect of HEAD Requests on Various Servers
Test the Effect of HEAD Requests on Various Servers
- State:
- closed
- Person:
- François Daoust
- Due on:
- July 16, 2008
- Created on:
- March 13, 2008
- Associated Product:
- Guidelines for Web Content Transformation Proxies
- Related emails:
- [minutes] CT Call Tuesday 2 December 2008 (from fd@w3.org on 2008-12-02)
- RE: [agenda] CT Call 2 December 2008 (from SPatterson@Novarra.com on 2008-12-02)
- RE: [agenda] CT Call 2 December 2008 (from SPatterson@Novarra.com on 2008-12-02)
- [agenda] CT Call 2 December 2008 (from fd@w3.org on 2008-12-01)
- [agenda] CT Call 25 November 2008 (from fd@w3.org on 2008-11-24)
- [minutes] BPWG 2008-11-13 (from fd@w3.org on 2008-11-13)
- ACTION-710: Test the effect of HEAD Requests on Various Servers (from fd@w3.org on 2008-11-13)
- [minutes] Thursday July 24 teleconf (from dom@w3.org on 2008-07-24)
- [minutes] CT Call Tuesday 10 June 2008 (from fd@w3.org on 2008-06-10)
- Re: [agenda] CT Call Tuesday 10 June 2008 (from fd@w3.org on 2008-06-10)
- [minutes] Thursday 20 February 2008 Teleconf (from fd@w3.org on 2008-03-20)
Related notes:
(this was meant to be raised at the F2F but Trackbot dropped the ball on it)
Jo Rabin, 13 Mar 2008, 12:32:53I need to come up with a real report on this, but the tests I've done so far show that a HEAD request is treated exactly the same way as a GET request in most server pages systems (ASP, JSP, PHP, ...). The difference between HEAD and GET is handled by the underlying web server (Apache, Jigsaw, IIS, ...) that only returns the HTTP headers and not the response body.
In short: when given a HEAD, the server gets over-excited.
Display change log.