I clicked over to the Session Inspector tab of Fiddler to view the raw HTTP response of each of the JS requests. Sure enough, there is a request for http://feeds.adobe.com/uber/js/omtr_tc.js which returns an HTML page stating, "The page you are looking for might have been removed, had its name changed, or is temporarily unavailable."
I viewed source for the main feeds.adobe.com page, but didn't see the omtr_tc.js file name anywhere. It must be included from another JS file.
I scanned back through my JS files, and noticed one located at http://www.macromedia.com/uber/js/omniture_s_code.js which sends back a 301 redirect to http://www.adobe.com/uber/js/omniture_s_code.js.
Sure enough, omniture_s_code.js references our missing file with this path:
So what's the problem here? Our base URL for the main page is http://feeds.adobe.com/ but our JS file is located at http://www.adobe.com/ For the record, http://www.macromedia.com/uber/js/omtr_tc.js provides an 301 redirect to the www.adobe.com location.
So the moral of the story-- watch out when you include JS files from one domain to another when they contain relative URLs in them. I can think of 3 fixes off the top of my head:
- Copy the JS files to feeds.adobe.com or create a virtual directory for them.
- Put a 301 redirect in place at feeds.adobe.com to point to www.adobe.com
- Edit the JS files at www.adobe.com to have fully qualified path names in them.
Mystery solved. I guess I need to go dig out someone's E-mail address now to bug about this. Maybe I can mention the ridiculous amount of Arabic(?) recent searches on their home page. Are those for real??