The browser definitely is looking for a favicon, but I really don't think that has anything to do with the extra request to the home page. The behavior described with this bug is exactly what Zakas described in the empty image "src" attribute problem. Specifically:
1) In IE, an extra request is issued for the directory containing the file. 2) In WebKit, an extra request is issued for the page hosting the malfunctioning script or img tag. 3) In Firefox 3.6, no extra requests are issued. You can verify this using Charles or Fiddler. Regardless, when I do have the page with the AJAX search API on it, the second request is issued. As soon as the AJAX search API is removed, the stray request is never issued and our servers actually have some room breathe again since the load practically drops by half! You can see this if you look at the source for the two pages; the only difference between the two is that the API search loader is commented out. This only started happening in the last few days. I'm really hoping that a Google engineer will take notice of it and fix it soon! Andrew On Mar 26, 11:47 am, Jeremy Geerdes <[email protected]> wrote: > Looking at your page in both Safari and Chrome (which both use WebKit's > built-in inspector), I am seeing your stray request, but I don't think it has > to do with the API. Rather, I think it's that the browser is looking for a > favicon.ico and finding nothing. You might use a meta tag to specify one and > see if that doesn't eliminate the mysterious request (you would still see the > request for the favicon, but the mystery request would be gone). -- You received this message because you are subscribed to the Google Groups "Google AJAX APIs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-ajax-search-api?hl=en.
