Geocoder results in 403 for some customers
131 views
Skip to first unread message
F. Wiegerinck
Nov 30, 2009, 4:04:57 AM11/30/09
to Google Maps JavaScript API v3
A few of my customers are complaining about a non-working prototype.
After investigating the errors with firefox (+firebug) I discoverd
that they received a HTTP 403: "Your client does not have permission
to get URL: <url>". Other customers do not have this problem, which
suggests no errors in the javascript. Also this error is not limited
to the prototype, also the example pages found at code.google.com have
the same error.
I do not have a link to the prototype as it is not (yet) public
available. But access these public links results in the same error
condition:
http://code.google.com/intl/nl/apis/maps/documentation/v3/
http://code.google.com/intl/nl/apis/maps/documentation/v3/examples/geocoding-simple.html
(just press "geocode")
The browsers used for testing are IE7, IE8 and Firefox 3.5.
Anyone a suggestion? or how can I proceed to fix these problems for
the customers?
After investigating the errors with firefox (+firebug) I discoverd
that they received a HTTP 403: "Your client does not have permission
to get URL: <url>". Other customers do not have this problem, which
suggests no errors in the javascript. Also this error is not limited
to the prototype, also the example pages found at code.google.com have
the same error.
I do not have a link to the prototype as it is not (yet) public
available. But access these public links results in the same error
condition:
http://code.google.com/intl/nl/apis/maps/documentation/v3/
http://code.google.com/intl/nl/apis/maps/documentation/v3/examples/geocoding-simple.html
(just press "geocode")
The browsers used for testing are IE7, IE8 and Firefox 3.5.
Anyone a suggestion? or how can I proceed to fix these problems for
the customers?
Mike Williams
Nov 30, 2009, 12:01:03 PM11/30/09
to google-map...@googlegroups.com
Individual instances of exceeding the geocoder quota or speed limit give
error 620 but I believe that persistent abuse might possibly cause
Google to return 403.
See: http://code.google.com/apis/maps/faq.html#geocoder_limit
"If excessive geocoder usage continues, access to the Google Maps API
geocoder from this IP address may be blocked permanently."
--
Mike Williams
Gentleman of Leisure
error 620 but I believe that persistent abuse might possibly cause
Google to return 403.
See: http://code.google.com/apis/maps/faq.html#geocoder_limit
"If excessive geocoder usage continues, access to the Google Maps API
geocoder from this IP address may be blocked permanently."
--
Mike Williams
Gentleman of Leisure
F. Wiegerinck
Nov 30, 2009, 3:06:51 PM11/30/09
to Google Maps JavaScript API v3
Anyone a suggestion where I can determine if this is blocked due to
excessive geocoder usage?
I can't find any contact address to ask my question. Only the
suggestion to ask in this forum...
excessive geocoder usage?
I can't find any contact address to ask my question. Only the
suggestion to ask in this forum...
Ben Appleton
Nov 30, 2009, 4:45:10 PM11/30/09
to google-map...@googlegroups.com
Thanks - I'm guessing the error is that these customers are behind a proxy server which appends URL parameters such as "&safe=on". There's been a regression in our URL parser which has started to reject URLs with unknown parameters. The fix should go live in the next week. Sorry for the inconvenience!
Ben
--
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.
Rehan Iftikhar
Dec 7, 2009, 12:18:01 PM12/7/09
to Google Maps JavaScript API v3
Hello
I am experiencing the same issue. We are getting 403 errors on our
production site but not on our testing site. The code is the same. Do
we know when to expect a fix?
-Rehan
On Nov 30, 1:45 pm, Ben Appleton <apple...@google.com> wrote:
> Thanks - I'm guessing the error is that these customers are behind a proxy
> server which appends URL parameters such as "&safe=on". There's been a
> regression in our URL parser which has started to reject URLs with unknown
> parameters. The fix should go live in the next week. Sorry for the
> inconvenience!
>
> Ben
>
> > .
I am experiencing the same issue. We are getting 403 errors on our
production site but not on our testing site. The code is the same. Do
we know when to expect a fix?
-Rehan
On Nov 30, 1:45 pm, Ben Appleton <apple...@google.com> wrote:
> Thanks - I'm guessing the error is that these customers are behind a proxy
> server which appends URL parameters such as "&safe=on". There's been a
> regression in our URL parser which has started to reject URLs with unknown
> parameters. The fix should go live in the next week. Sorry for the
> inconvenience!
>
> Ben
>
> On Mon, Nov 30, 2009 at 8:04 PM, F. Wiegerinck <fwiegeri...@gmail.com>wrote:
>
> > A few of my customers are complaining about a non-working prototype.
> > After investigating the errors with firefox (+firebug) I discoverd
> > that they received a HTTP 403: "Your client does not have permission
> > to get URL: <url>". Other customers do not have this problem, which
> > suggests no errors in the javascript. Also this error is not limited
> > to the prototype, also the example pages found at code.google.com have
> > the same error.
>
> > I do not have a link to the prototype as it is not (yet) public
> > available. But access these public links results in the same error
> > condition:
> >http://code.google.com/intl/nl/apis/maps/documentation/v3/
>
> >http://code.google.com/intl/nl/apis/maps/documentation/v3/examples/ge...
>
> > A few of my customers are complaining about a non-working prototype.
> > After investigating the errors with firefox (+firebug) I discoverd
> > that they received a HTTP 403: "Your client does not have permission
> > to get URL: <url>". Other customers do not have this problem, which
> > suggests no errors in the javascript. Also this error is not limited
> > to the prototype, also the example pages found at code.google.com have
> > the same error.
>
> > I do not have a link to the prototype as it is not (yet) public
> > available. But access these public links results in the same error
> > condition:
> >http://code.google.com/intl/nl/apis/maps/documentation/v3/
>
> > (just press "geocode")
>
> > The browsers used for testing are IE7, IE8 and Firefox 3.5.
>
> > Anyone a suggestion? or how can I proceed to fix these problems for
> > the customers?
>
> > --
>
> > 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<google-maps-js-api-v3%2Bunsu...@googlegroups.com>
>
> > The browsers used for testing are IE7, IE8 and Firefox 3.5.
>
> > Anyone a suggestion? or how can I proceed to fix these problems for
> > the customers?
>
> > --
>
> > 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
> > .
Brian
Dec 17, 2009, 7:26:57 PM12/17/09
to Google Maps JavaScript API v3
Hey,
We're getting the same error as well.
Brian
> > > google-maps-js-a...@googlegroups.com<google-maps-js-api-v3%2B unsub...@googlegroups.com>
Reply all
Reply to author
Forward
0 new messages