Dear Mike, You seem to have understood the problem I am facing very well. I wanted to register this as a problem, but I couldn't find any quick links to do so.
Mr. Igloo, I have no problems if the map doesn't work when I try with "local" copy. Without closing the session of the browser, when I change the URL which is registered, then I am expecting the map to load. you want the map to load right? As mentioned by Mike, the cache should be cleared and the validation of the URL to decide whether to load the map or not should happen on the server side. Or atleast, cache should be cleared. Dear Larry, Thanks for the comments. My dear Andrew, If you can see, I have mentioned "I request someone to look into this issue and resolve" If you are heart, I am really sorry... I hope you have read the comments wirtten by Mr. Mike. "I would greatful" If any one can tell me how to register this in the issues list. Thanks a lot for the comments once again. -- Amarnath On Oct 14, 6:57 pm, Mike Williams <[EMAIL PROTECTED]> wrote: > One possibility is that it's a cache issue. > > Because you're calling the API loader with an identical request, with > even the key the same, then your browser is perfectly entitled to return > the old version of the code from its cache. > > That didn't matter in the past, because the key validation was performed > in the main client side code, using the current value of > window.location.host, and would succeed when rerun against the correct > site. > > Recently, server side key validation has been introduced. If the server > side validation fails, then the loader code that gets returned will > display the error. A *fresh* call on the correct site will pass the key > validation test, but if you run the old copy of the code from your > browser cache, then it will still fail, because the failure message is > burned into the cached code. > > Quick fix: When this occurs on one of your PCs, use Ctrl-Shift-Refresh > to force a fresh fetch of the loader code. (Or use a browser that has > less aggressive caching, like Firefox). > > If that works, but you're not satisfied with using that as a workround, > then I suggest you raise it as an issue. Google could easily modify > their Cache-Control settings in such a way that the loader code doesn't > get cached. > > --http://econym.org.uk/gmap > The Blackpool Community Church Javascript Team --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
