No, that was my fault. I skimmed right past all the mentioning of the Maps API stuff!
Anyway, I could be wrong (again) but I think the key validator just checks the key hash against its database to make sure that the http referer matches. I would double check that the key was registered for the same address that you use to access it internally. For instance, if you registered it for serverx.mydomain.com because that's how the box is referenced externally, but internally, you're calling it by an IP address or other, you will come up with the mismatched key message. Another way around this would be to move your dev environment onto a single local machine. You can register keys for localhost. Alternatively, files opened directly in the browser (i.e., through File -> Open) don't even check the key; it's assumed you're using it for dev. Jeremy R. Geerdes Effective website design & development Des Moines, IA For more information or a project quote: http://jgeerdes.home.mchsi.com [email protected] If you're in the Des Moines, IA, area, check out Debra Heights Wesleyan Church! On Feb 11, 2010, at 4:06 PM, College of Sciences Web Support wrote: > I should have put this, it is the maps API that we are using. I am > assuming that google is making some sort of request back to us to send > map data correct? Sorry about the incomplete post, its nearing the end > of the day here :). > > Matt > > On Feb 11, 4:33 pm, Jeremy Geerdes <[email protected]> wrote: >> Skip the key. Just don't provide it, and it'll work. The key is optional for >> all but the Maps API anyway. >> >> Jeremy R. Geerdes >> Effective website design & development >> Des Moines, IA >> >> For more information or a project quote:http://jgeerdes.home.mchsi.com >> [email protected] >> >> If you're in the Des Moines, IA, area, check out Debra Heights Wesleyan >> Church! >> >> On Feb 11, 2010, at 3:29 PM, College of Sciences Web Support wrote: >> >> >> >>> Hi everyone, >> >>> We are working on a server that is not open to the world on any ports. >>> It is an internal dev server and is only open to ip's within our >>> building. If we are trying to implement google ajax api do we have to >>> have port 80 open for google to do some form of communication with it? >> >>> We checked the host to make sure it was requesting correctly and it >>> is, we also have tried to register a key for the domain, subdomain and >>> directory, and none have worked we get the message: >> >>> This web site needs a different Google Maps API key. A new key can be >>> generated athttp://code.google.com/apis/maps/. >> >>> we used the code: >>> <script src="http://maps.google.com/maps? >>> file=api&v=2&sensor=false&key=ourkey" type="text/ >>> javascript"></script> >> >>> with "ourkey" replaced by the appropriate key. >> >>> I can potentially get port 80 opened up, but I need to know for a fact >>> that it needs to be for our testing purposes before IT here will do >>> it. >> >>> Thanks for any help >>> Matt >> >>> -- >>> 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 >>> athttp://groups.google.com/group/google-ajax-search-api?hl=en. > > -- > 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. > -- 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.
