This forum is a discussion about improving the "How does built-in Phishing and Malware Protection work?" article. If you'd like to participate, please register.

If you need help with Firefox, please ask a question.

Developer's Guide (DEPRECATED v2.2)

  • 10 Replies
  • Last reply by TyDraniu
  1. Joergen 25 posts
    Report Abuse
    Hi Shouldn't this link in the article https://developers.google.com/safe-browsing/developers_guide_v2 be changed to https://developers.google.com/safe-browsing/developers_guide_v3
  2. guigs 598 posts
    Report Abuse

    Yes, I just checked a recent list manager bug to make sure that it was updated before the API was deprecated.

    Inference: 2.2 example HTTP List Call for Safe Browsing API

    http://safebrowsing.clients.google.com/safebrowsing/list?client=api&apikey=APIKEY&appver=CLIENTVER&pver=PVER&wrkey=MACKEY

    3.0 example HTTP List Call for Safe Browsing API https://safebrowsing.google.com/safebrowsing/list?client=api&key=APIKEY&appver=CLIENTVER&pver=PVER


    Request log taken from bug:[ https://bugzilla.mozilla.org/show_bug.cgi?id=997872#c2] [listmanager] Set update url: https://safebrowsing.google.com/safebrowsing/downloads?client=Firefox&appver=31.0a1&pver=2.2&key=no-google-api-key [listmanager] Set gethash url: https://safebrowsing.google.com/safebrowsing/gethash?client=Firefox&appver=31.0a1&pver=2.2 SafeBrowsing: addMozEntries: n:1000

    The format being used is version 3.0, however it may have been easier to assume that since it is still working that this is the api being used.

    Yes, I just checked a recent list manager bug to make sure that it was updated before the API was deprecated. Inference: 2.2 example HTTP List Call for Safe Browsing API http://safebrowsing.clients.google.com/safebrowsing/list?client=api&apikey=APIKEY&appver=CLIENTVER&pver=PVER&wrkey=MACKEY 3.0 example HTTP List Call for Safe Browsing API https://safebrowsing.google.com/safebrowsing/list?client=api&key=APIKEY&appver=CLIENTVER&pver=PVER Request log taken from bug:[ https://bugzilla.mozilla.org/show_bug.cgi?id=997872#c2] [listmanager] Set update url: https://safebrowsing.google.com/safebrowsing/downloads?client=Firefox&appver=31.0a1&pver=2.2&key=no-google-api-key [listmanager] Set gethash url: https://safebrowsing.google.com/safebrowsing/gethash?client=Firefox&appver=31.0a1&pver=2.2 SafeBrowsing: addMozEntries: n:1000 The format being used is version 3.0, however it may have been easier to assume that since it is still working that this is the api being used.
  3. guigs 598 posts
    Report Abuse

    There might be a question if the other urls are working as well, but it does not look like these have changed.

    There might be a question if the other urls are working as well, but it does not look like these have changed.
  4. guigs 598 posts
    Report Abuse

    So it seems as if the older versions of Firefox with the older version of the API may no longer work. Can we add a warning to users in this, or maybe a "show for " and version before December 2014?

    So it seems as if the older versions of Firefox with the older version of the API may no longer work. Can we add a warning to users in this, or maybe a "show for " and version before December 2014?
  5. Francois Marier 0 posts
    Report Abuse

    Firefox is still using version 2.2 of the protocol and we'll stay on that version until we move to version 4 (https://bugzilla.mozilla.org/show_bug.cgi?id=1167038).

    Firefox is still using version 2.2 of the protocol and we'll stay on that version until we move to version 4 (https://bugzilla.mozilla.org/show_bug.cgi?id=1167038).
  6. TyDraniu 3 posts
    Report Abuse

    For the clarity: Link https://developers.google.com/safe-browsing/developers_guide_v2 points to https://developers.google.com/safe-browsing/, where are links to v4 (actual API) and v3 (deprecated API). There's no v2 API at all, So we can't say " The technical details of the safe-browsing protocol are also publicly available.", because they are not.

    For the clarity: Link https://developers.google.com/safe-browsing/developers_guide_v2 points to https://developers.google.com/safe-browsing/, where are links to v4 (actual API) and v3 (deprecated API). There's no v2 API at all, So we can't say " The technical details of the safe-browsing protocol are also [https://developers.google.com/safe-browsing/developers_guide_v2 publicly available].", because they are not.
  7. Francois Marier 0 posts
    Report Abuse

    Ah that's annoying. It looks like they removed the V2 docs when they published V4 last week :(

    I suppose we should just remove that sentence then.

    Ah that's annoying. It looks like they removed the V2 docs when they published V4 last week :( I suppose we should just remove that sentence then.
  8. AliceWyman 4805 posts
    Report Abuse

    TyDraniu said

    For the clarity: Link https://developers.google.com/safe-browsing/developers_guide_v2 points to https://developers.google.com/safe-browsing/, where are links to v4 (actual API) and v3 (deprecated API). There's no v2 API at all, So we can't say " The technical details of the safe-browsing protocol are also publicly available.", because they are not.

    https://developers.google.com/safe-browsing/ has two links at the bottom: Safe Browsing APIs (v4) https://developers.google.com/safe-browsing/v4/ Safe Browsing APIs (v3) https://developers.google.com/safe-browsing/v3/index

    ''TyDraniu [[#post-13725|said]]'' <blockquote> For the clarity: Link https://developers.google.com/safe-browsing/developers_guide_v2 points to https://developers.google.com/safe-browsing/, where are links to v4 (actual API) and v3 (deprecated API). There's no v2 API at all, So we can't say " The technical details of the safe-browsing protocol are also [https://developers.google.com/safe-browsing/developers_guide_v2 publicly available].", because they are not. </blockquote> https://developers.google.com/safe-browsing/ has two links at the bottom: Safe Browsing APIs (v4) https://developers.google.com/safe-browsing/v4/ Safe Browsing APIs (v3) https://developers.google.com/safe-browsing/v3/index
  9. TyDraniu 3 posts
    Report Abuse

    AliceWyman said

    https://developers.google.com/safe-browsing/ has two links at the bottom: Safe Browsing APIs (v4) Safe Browsing APIs (v3)

    Yeah, I know, but neither of these APIs is used by Firefox, according to previous discussion.

    Are you sure, you want to leave this as is? I don't want to start translating before getting it final.

    ''AliceWyman [[#post-13730|said]]'' <blockquote> https://developers.google.com/safe-browsing/ has two links at the bottom: Safe Browsing APIs (v4) Safe Browsing APIs (v3) </blockquote> Yeah, I know, but neither of these APIs is used by Firefox, according to previous discussion. Are you sure, you want to leave this as is? I don't want to start translating before getting it final.
  10. AliceWyman 4805 posts
    Report Abuse

    TyDraniu said

    AliceWyman said
    https://developers.google.com/safe-browsing/ has two links at the bottom: Safe Browsing APIs (v4) Safe Browsing APIs (v3)

    Yeah, I know, but neither of these APIs is used by Firefox, according to previous discussion.

    Are you sure, you want to leave this as is? I don't want to start translating before getting it final.

    Sorry, I misunderstood your comment, where are links to v4 (actual API) and v3 (deprecated API). as a question.

    I approved the revision by Chris Ilias to remove the sentence that used to link to the v2 docs.

    ''TyDraniu [[#post-13737|said]]'' <blockquote> ''AliceWyman [[#post-13730|said]]'' <blockquote> https://developers.google.com/safe-browsing/ has two links at the bottom: Safe Browsing APIs (v4) Safe Browsing APIs (v3) </blockquote> Yeah, I know, but neither of these APIs is used by Firefox, according to previous discussion. Are you sure, you want to leave this as is? I don't want to start translating before getting it final. </blockquote> Sorry, I misunderstood your comment, ''where are links to v4 (actual API) and v3 (deprecated API).'' as a question. I approved the revision by Chris Ilias to remove the sentence that used to link to the v2 docs.
  11. TyDraniu 3 posts
    Report Abuse

    Thanks, Alice.

    Thanks, Alice.