Hi,
Not sure when V1 will be turned off but that URL looks like its come
from V1.
V2 uses the initial URL looking something like:
http://safebrowsing.clients.google.com/safebrowsing/downloads?client=api&apikey=".$this->apikey."&appver=".$this->version."&pver=".$this->apiversion
and then uses POST to request certain lists etc.
Whilst V1 (from what I know) gave entire massive lists; V2 serves the
database up in chunks which is quite a bit different and I recommend
if you're switching to V2 to read the docs thoroughly!
If you get stuck then this is the place to post :)
--Sam
On Jan 6, 11:46 am, walkerj <
walk1...@gmail.com> wrote:
> Hi Everyone,
>
> I've inherited some legacy code as the result of someone leaving our
> organization and now I need to find out if he did everything against V1 of
> the API or if he changed it to use V2. I believe he did the development at
> the beginning of 2010 or even the end of 2009 so I am suspecting it is V1 of
> the API. However, it is not easy to tell simply by looking at the code. The
> solution has been done using Java and xLightWeb. It's asynchronous code that
> isn't the easiest to follow but that probably is irrelevant. What I think is
> relevant is that it is using the following URL to make the request for the
> blacklist:
>
>
http://sb.google.com/safebrowsing/update?client=api&apikey=ABCDEFGuge...