Onderwerp: Re: [CODE4LIB] Restricted access fo free covers from Google :)
Hi Pete, I'd be interested in an update on this. Is your ProxyPass with
Apache to access Google Books search API still working well for you, and
not running into Google traffic limiters?You haven't actually
communicated
For what concerns Google's policy concerning NAT calls being treated as
spyware activity. I am now proxying Google for the JSON call, so it will
see the IP adress of our web server in stead of the Network Adress
Translator. It helps for the moment. Now I wonder if our own calls will
make Google
Wait, now ALL of your clients calls are coming from one single IP?
Surely that will trigger Googles detectors, if the NAT did. Keep us
updated though.
Jonathan
Boheemen, Peter van wrote:
For what concerns Google's policy concerning NAT calls being treated as
spyware activity. I am now
On Tue, 18 Mar 2008, Jonathan Rochkind wrote:
Wait, now ALL of your clients calls are coming from one single IP?
Surely that will trigger Googles detectors, if the NAT did. Keep us
updated though.
I don't know what Peter's exact implementation is, but they might relax
the limits when they see
: di 18-3-2008 18:48
Aan: CODE4LIB@LISTSERV.ND.EDU
Onderwerp: Re: [CODE4LIB] Restricted access fo free covers from Google :)
Nice. X-Forwarded-For would also allow google to deliver availability
information suitable for the actual location of the end-user. If their
software chooses to pay
I'd be very surprised if Google _automatically_ took any notice of
anything in an HTTP header to relax protection against what they
consider harvesting of data because all HTTP headers can be set to
anything: that is, if I wanted to suck Google dry of bib data, I
could simply pretend to be
