Confirmed users
158
edits
Security/Safe Browsing/V4 Implementation: Difference between revisions
Jump to navigation
Jump to search
m
Security/Safe Browsing/V4 Implementation (view source)
Revision as of 01:57, 3 October 2016
, 3 October 2016→Use custom API key
No edit summary |
|||
| Line 12: | Line 12: | ||
= Use custom API key = | = Use custom API key = | ||
We are required to have a API key to access google services like geolocation and safe browsing. The nightly/beta/aurora/release Firefox builds will have a proper API key associated with mozilla. However, if you are using the Firefox built on your own, the API key will be substituted with "no-google-api-key", which is apparently not available. There are a couple of ways to use a working API key for Safe Browsing. The most recommended way is to | We are required to have a API key to access google services like geolocation and safe browsing. The nightly/beta/aurora/release Firefox builds will have a proper API key associated with mozilla. However, if you are using the Firefox built on your own, the API key will be substituted with "no-google-api-key", which is apparently not available. There are a couple of ways to use a working API key for Safe Browsing. The most recommended way is to prepare a key file and add the path to mozconfig: | ||
# Obtain a Safe Browsing google API key from https://console.developers.google.com | # Obtain a Safe Browsing google API key from https://console.developers.google.com | ||