403 error from bad url

Question

Some of my customers are getting HTTP 403 errors as a result of bad urls.  Our site is not generating any of these URL's.  What is?  Is it the result of a bad browser, a bad registry or corrupt files?  All of the errors are coming from IE8.  Customers using other browsers are not having the issue.

Any ideas or suggestions?

thanks, Tony

The Bad Url
/myaccount/jscript/f%7B%20%20%20%20%20%20%20%20%20%20return%20'SS_SB_pad_350x60_070909.swf';%20%20%20%20%20%20%20%20%7D%20%20%20%20%20%20%20%20function%20getSS1Link()%20%7B%20%20%20%20%20%20%20%20%20%20return

User Agent
Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; InfoPath.1; IEMB3; .NET CLR 2.0.50727; Zune 3.0; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; WINFC 1.2.0.64)

Answer 1

Hi,

What Proxy software are your clients using? SQUID?

Do they share the same ISP? (AOL?)

One of your UA tokens (IEMB3) is currently under investigation to determine its origin.

http://www.google.com/search?q=IEMB3


Do you know what IE Addon that is?


Regards.

---

Rob^_^

Answer 2

Thanks for the reply.  

Here's what we found:

By looking at more recent Tea Leaf sessions, they are both using supported versions of IE.  GTB6 is an add-on that apparently stands for Google Tool Bar and is in the first customer’s user agent string.  I was not able to find any info on the second user agent but can assume AskTB5.3 is an Ask.com tool bar.  

26430140

HTTP_USER_AGENT=Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; GTB6; InfoPath.1)

42817237

HTTP_USER_AGENT=Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; AskTB5.3)

Another issue we’ve seen sporadically in some user agent strings is “YIE8” and by all accounts that is a Yahoo version of Internet Explorer.  These seem to be the only correlations to some unique situations creating website malfunctions.  These search engine add-ons, specifically YIE8, may have some parental controls or other browser settings inhibiting the functionality of our website.  

Using Tea Leaf I was not able to find any Proxy software information.  Neither customer seems to be using AOL but ISP is also undefined.