As long as you're abiding by the TOS, you don't really need the API key. Without the key, it should work. That said, the TOS do require that you or, in this case, your users provide a valid HTTP_REFERER header. Obviously, there may not be much that you can do to ensure that your clients are complying with this in the case of a JS app, but if you are expecting that more than a small minority of your users to be utilizing plug-ins like these, you may want to consult a legal expert of some kind to see what your obligations and liabilities will be under the TOS.
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 Sep 3, 2010, at 11:25 PM, Ono Oogami wrote: > Hello. > > For privacy consideration some people prevent their browsers from > sending real HTTP Referrer via some ways (e.g. using FireFox > "refcontrol" extension). As the Google JS API Key is valid only to a > certain domain and / or path, would Google JS API works on these > browsers ? > > -- > 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.
