I am getting a lot of incoming requests with this structure:
//domain_name/cache/22092e9b25c40809dfb94b6179166b26.
I am running a .NET 4.0 website served from IIS 7.5. A lot of these URLs have no referrer URLs and come in randomly with a different 32 digit alphanumeric key. And I do not have any resource like '.../cache/...' on my website.
I just want to eliminate such requests and want to understand where these are coming from at all. Any help would be appreciated.
It seems that Chrome browser had a bug (Issue 132059:) http://code.google.com/p/chromium/issues/detail?id=132059 for specific versions (19.0.1084.52-2 19.0.1084.56 not with 18.xx)
BUT: i found on my server, that CHROME users, still sending those requests, even with NEWER chrome version. (Chrome/22.0.1229.94)
Logs from 2012-10-21
188.6.141.189 - - [21/Oct/2012:08:51:04 +0100] "GET /{{MYPAGE}}/cache/99e668d4c3ad55d2f2c876540bf3e7e6 HTTP/1.1" 200 16307 "http://{{MYSERVER}}/{{MYPAGE}}" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4"
95.233.53.220 - - [21/Oct/2012:08:55:01 +0100] "GET /cache/4d8f7265aa32291438a3a9b9e158f843 HTTP/1.1" 404 1376 "http://{{MYSERVER}}/{{MYPAGE}}" "Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4"
80.99.63.141 - - [21/Oct/2012:08:56:34 +0100] "GET /{{MYPAGE}}/cache/575c44ac6fcb338b52bac212665cb165 HTTP/1.1" 200 16307 "http://{{MYSERVER}}/{{MYPAGE}}" "Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4"
78.1.148.185 - - [21/Oct/2012:08:56:41 +0100] "GET /{{MYPAGE}}/cache/3ee13ff1e23d8873ddb0e0042c6a3910 HTTP/1.1" 200 16229 "http://{{MYSERVER}}/{{MYPAGE}}" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4"
80.180.181.64 - - [21/Oct/2012:09:00:41 +0100] "GET /cache/c4f56b1faa9ea9bb7789728409bfc21f HTTP/1.1" 404 1376 "http://{{MYSERVER}}/{{MYPAGE}}" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4"
79.36.123.193 - - [21/Oct/2012:09:05:19 +0100] "GET /cache/11ff17cacc601d7ee9790cb2933e86c9 HTTP/1.1" 404 1376 "http://{{MYSERVER}}/{{MYPAGE}}" "Mozilla/5.0 (Windows NT 6.0) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4"
5.102.21.234 - - [21/Oct/2012:09:06:54 +0100] "GET /{{MYPAGE}}/cache/fc8ccc9bd6e960b7e4f4af0165e839a6 HTTP/1.1" 200 16386 "http://{{MYSERVER}}/{{MYPAGE}}" "Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4"
149.210.41.194 - - [21/Oct/2012:09:07:05 +0100] "GET /{{MYPAGE}}/cache/4e4055517809a8bbc8de1acb4ee9e560 HTTP/1.1" 200 15998 "http://{{MYSERVER}}/{{MYPAGE}}" "Mozilla/5.0 (Windows NT 6.0) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4"
It might be,
1] Chrome still have this bug i mentioned.
2] Some Chrome ADD-ON/EXTENSION is sending those requests.