Welcome to WebmasterWorld Guest from 18.104.22.168
22.214.171.124 - - [10/Sep/2008:21:15:58 -0400] "GET /scripts/menu.js HTTP/1.0" 403 - "http://www.apassion4jazz.net/jazz_styles.html" "User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; GoogleT5; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; .NET CLR 3.0.04506; InfoPath.2; Tablet PC 2.0)"
This got blocked because of the "User-Agent:" part which I filter due to SPAMers pounding my input forms.
Yes, I'm a big meanie ;)
Because of this, I've been serving a small page with a note about our site not supporting pre-fetching. The page includes CSS and image references which are never fetched by these user-agents. However, there is frequently another session immediately following from the same IP address, where the user-agent and browsing behaviour is completely normal and human-like.
However, after taking a look at Tapestry, I've modified the logic to block any UA starting with "User-agent" unless it starts with "User-agent: Mozilla/4.0 (compatible; MSIE 6.0;". This would block the UA being discussed here based on the MSIE version -- without requiring a "T5"-specific pattern, although it might be a good idea to include such a pattern.