每个Google Maps API密钥的引荐来源网址限制 [英] Referrer limit per google-maps api key

问题描述

我们为2500多家客户提供网站/CMS解决方案.几乎所有网站都有google-map模块.因此，由于Google更改了地图使用政策，因此从一天到另一天，所有这些网站的地图模块均出现错误.我们需要提出一些快速(又肮脏)的解决方案.我们决定使用多个api键，并在它们之间分配域-字母.而且，我们在这些密钥下手动注册了所有这2500多个域.一对一.

We are providing websites/CMS solutions for more than 2500 customers. Almost all websites have google-map module. So since google changed its map usage policy, from one day to another all those webs had an error on their map modules. We need to come up with some quick (and dirty) solution. We decided to use multiple api-keys, and devide domains between them - alphabetic. And we registered all those 2500+ domains under these keys - manually. One by one.

该解决方案一直有效到上周.现在我们以某种方式达到了某种极限，因为我们无法在这些api密钥之一下注册任何新的域/引荐来源.该给定api-key的域/引荐来源网址的实际计数:1537.保存过程会产生跟踪代码错误(这是我每次尝试的次数都不一样).

The solution worked until last week. Now we somehow reached some kind of limit, as we cannot register any new domains/referrers under one of those api-keys. The actual count of domains/referrer of this given api-key: 1537. The saving process yields an error with tracking code (which is every time I try different).

真的有某种限制吗?有没有人遇到过同样的问题.是否存在一些省时的解决方案?

Is there really some kind of limit? Does anyone experienced the same problems. Does some time-economic solution exists?

感谢您的帮助或建议.和平！

Thanks for any help or suggestions. Peace!

推荐答案

(在撰写本文时)每个API密钥确实存在大约1,000个引用者限制.您可以为每个项目创建约100个密钥，因此您可以通过一个项目对100,000个域进行身份验证.要进一步进行操作，您可以创建多个项目(请注意，多个项目可以在同一个帐单帐户下合并，因此您仍然会收到一个帐单).

There is indeed a limit of (at time of writing) about 1,000 referer restrictions per API key. You can create about 100 keys per project, so you can authenticate 100,000 domains with a single project. To proceed further, you can create multiple projects (note that multiple projects can be combined under the same billing account, so you would still receive a single bill).

作为一项短期解决方案，您可以暂时删除对该密钥的所有限制，以便依赖该密钥的应用程序可以重新运行.然后，您可以花时间按照这些准则发布新的密钥分片模式.

As a short term fix, you can temporarily remove all restrictions on the key, so that apps relying on that key are functional again. Then you can take the time to release a new key sharding pattern that follows these guidelines.

我刚刚创建了功能请求这样就可以改善这种用例的情况(将其标记为星标"，以通知更新).

I just created a feature request so that the situation can be improved, for this use case ("star" it, to be notified of updates).

这篇关于每个Google Maps API密钥的引荐来源网址限制的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！