No such of a thing, whatever the method of addressing a
server which
collects data then follows up with setup institutions has
nothing to
do with a customer. A customer being returned to where he
was before
the checkout occurs has really nothing to do with a IP
address range.
You are thinking of what a router does, this situation does
not found
a range of IP addresses only used by Google Checkout, if you
block IP
address ranges on a router the result will be that some
people whom
rely on other IP addresses within those ranges cannot access
what they
are or have been accessing, maybe they don't have a Google
need and
this is really out of their range for the sessions they
experience No
one shops and checksout all day long. Its like this a
"robot does not
purchase merchandise".
On Dec 19, 8:18 am, michael-cbf <cbf.salest... googlemail.com> wrote:
> For security reasons we wish to restrict the IP ranges
that are
> allowed to access the scripts called by the google
checkout callback
> servers.
>
> I've had a look in the API docs, but I can't find the
ip ranges listed
> anywhere.
>
> Where can I find a list of the IP ranges that google
use for
> callback / notification requests ?
>
> Michael
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "API Integration Basics" group.
To post to this group, send email to
google-checkout-api-integrationgooglegroups.com
To unsubscribe from this group, send email to
google-checkout-api-integration-unsubscribegooglegroups.com
For more options, visit this group at http://groups.google.com/group/google-checko
ut-api-integration?hl=en
-~----------~----~----~----~------~----~------~--~---
|