The Version 2 system used the referrer as well, but defaulted to
"allow" where there wasn't one. In this case it would be helpful if
the message was more explicit, because in your scenario the key is not
wrong.
I can't see the issue with using the referrer for the API. The
referrer which is calling the API will always be the domain you're
looking at and there should be nothing which identifies you, so there
is no privacy issue. [The IP address could be used to identify you,
but only with some difficulty]
In fact, I'm not really sure what the privacy issue is at all. Why do
you suppress the referrer header?
My browser is not allowed to give away the referrer. This is for (my
own) security resons and to protect (my own) privacy.
Thanks. I'll test and get back to you.
Note that the new keys support wildcard referrer filtering.
Chris
--
You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group.
To post to this group, send email to google-map...@googlegroups.com.
To unsubscribe from this group, send email to google-maps-js-a...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.