On Sep 17, 2:37 pm, Mike Williams <[EMAIL PROTECTED]> wrote: > What seems to be going on is that if the API loader thinks that you're > using Google Maps Premiere it uses an entirely different loading > mechanism. The free API loader performs the key validation in > Javascript. The Premiere API loader performs the key validation in the > server. > > MSIE caches the loader code, which it is entitled to do as long as it > only caches it on your local machine. The "Cache-Control: private" flag > in the header only tells it not to store it in any shared cache or > proxy.
This would indicate a client-side problem? I've done everything today using Chrome (so it would appear not to be due to IE's aggressive caching). What is odd is that the maps which are flagged here as failing also fail for me, with the Premier message; and others work fine. Andrew --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" 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-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
