Workaround for Google Geocoding API restrictions? Why no HTTP referrers?

This topic contains 2 replies, has 2 voices, and was last updated by  Mark Murphy 3 years, 12 months ago.

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket

Tagged: 

  • Author
    Posts
  • #542972

    Mark Murphy
    Free User
    Post count: 1

    I have a subscription for Location Manager Extension.

    Wordpress: 5.4
    GeoDirectory Core: 2.0.0.90
    GeoDirectory Location Manager: 2.0.0.25

    According to the GD Docs, the Google Geocoding API Key “must not be restricted with HTTP referrer rules.”

    I have discovered if I use any HTTP referrer rules, I receive map error messages like
    No Records Found
    Sorry, no records were found. Please adjust your search criteria and try again.”

    If I remove the HTTP referrer rule, everything works fine.

    Here are my questions:

    1. Why must the Geocoding API key not be restricted? Google warns that without HTTP referrer restrictions, you may be exposed to key theft or misuse as the key is exposed in the HTTP page source.

    2. Is there a workaround or other method to prevent potential Geocoding API key exposure in this way? Is the Geocoding API key exposed in the page source or other places?

    3. I am posting this request in the Multilocation Add-on forum, although the extension is called “Location Manager”. Should this be corrected?

    Thank you,

    Mark Murphy
    Herndon, VA
    US

    #543122

    Alex Rollin
    Moderator
    Post count: 27815

    A valid license is required to view this reply.

    You may need to login

    OR

    Buy either a Membership or valid license for this product.

    Thanks, Team GeoDirectory!

    #543139

    Mark Murphy
    Free User
    Post count: 1
    This reply has been marked as private.
Viewing 3 posts - 1 through 3 (of 3 total)

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket