While you wait for the bug to be fixed, consider this temporary experimental workaround to suppress the extra requests:
First, change all relative URIs to absolute URIs, throughout the page(s) where you load the search API. Then add a BASE element specifying a nonexistent domain. Example: HTML: <base href="http://nonexistent-domain.com/"> XHTML: <base href="http://nonexistent-domain.com/" /> Place that element in the HEAD section (prior to any other element therein that refers to an external URI). Check again to make sure that all URIs specified in the document are absolute (e.g. "http://..."). Test the modified page(s) in Webkit, IE, and any other type of browser where you previously observed the extra requests. (Disclaimer: This workaround is experimental. I don't know if specifying a bogus base might cause unwanted side-effects. In any case, this obviously isn't the proper or intended usage of the base element. Use this workaround entirely at your own risk, and only if you consider it absolutely necessary to suppress the extra requests while you wait for the API bug to be fixed.) -- omr -- 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.
