Browser Key Issues

  • Resolved mbigler

    (@mbigler)


    7 years, 2 months ago

    The plugin doesn’t seem to work when an HTTP referrer restriction is set on the Browser Key; so, I’m only able to use it when the key is unrestricted. I’ve followed the instructions for creating the browser key and set the HTTP referrer to point to my domain using the * wildcard as directed, but when I do that the console reports an error that the site isn’t authorized and lists the domain to add to the referrer list. After adding the domain as it is displayed in the error, the issue persists. I’ve tried every variation I can think of, even listing each page individually, but haven’t had any luck.
    I’d like to be able to use this plugin without allowing the world to use my API key, how can I do that?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Tijmen Smit

    (@tijmensmit)

    7 years, 2 months ago

    The referrer for the browser key should be in this format domain.com/*, you don’t necessarily need to include http or https.

    But it can take 5 minutes or more before changes are processed by Google, and in some cases creating a new key is the only solution. So instantly trying if the browser key works can fail is some cases.

    Thread Starter mbigler

    (@mbigler)

    7 years, 2 months ago

    Thanks, I thought I was waiting long enough but evidently not; it’s all good now.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Browser Key Issues’ is closed to new replies.