Forum Moderators: open

Message Too Old, No Replies

Not a real HEAD request?

         

wilderness

4:06 am on Aug 1, 2006 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Not sure if this is the user or the IP.
There wasn't a real head request, however that's obviously what the second request is.

All this on a page with no-cache.

24.49.192.#*$! - - [31/Jul/2006:18:35:03 -0700] "GET /myfolder/mySubfoler/mypage.html HTTP/1.1" 200 12861 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; FunWebProducts; .NET CLR 1.1.4322)"
24.49.192.#*$! - - [31/Jul/2006:18:35:04 -0700] "GET /SameFolder/SameSubfoler/SamePage.html HTTP/1.1" 200 0 "-" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; FunWebProducts; .NET CLR 1.1.4322)"

Lord Majestic

12:53 am on Aug 4, 2006 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Modern browsers often use If-Modified-Since header in GET requests - this allows server to decide (for static files) whether to send data or not. Ages ago browsers first used HEAD request to check if document changed, but now its done in GET request thus avoiding costs of making extra request.

There is no refer however and time difference between requests is very small, so it might not be human browser.

[edited by: Lord_Majestic at 12:53 am (utc) on Aug. 4, 2006]

thetrasher

10:35 am on Aug 4, 2006 (gmt 0)

10+ Year Member



If-Modified-Since results in 200 + data or 304 (= not modified).

I think the response without (body) data was produced by disconnection after receiving your HTTP header.