Slashdot Mirror


The Internet Archive Switches To HTTPS Connections By Default

An anonymous reader writes "The Internet Archive today announced it has enabled HTTPS connections by default on archive.org and openlibrary.org. The organization today also revealed it now sees over 3 million users per day. Both sites are still accessible over HTTP connections. Since the Wayback Machine is hosted on archive.org, it also follows the same rules: the secure version is used by default, but you can use the http version which will help load certain complicated webpages."

3 of 40 comments (clear)

  1. Re:Advertisements by claar · · Score: 3, Insightful

    So get the ad companies to serve the ads over HTTPS... I don't see the big deal.

    --
    I'd give my right arm to be ambidextrous...
  2. Re:Internet Archive leaves /. behind by cffrost · · Score: 3, Insightful

    When your government regards YOU as their biggest enemy,

    Yes...

    and YOU should thus consider them in reverse,

    Uh huh...

    https is a false sense of security.

    No, it's partially broken, vulnerable-to-attack security, whereas HTTP is completely vulnerable, bare-naked plaintext — nothing to break, no certs to MITM, no bribing CAs for keys — zero security.

    As bad as HTTPS may be, comparing it to HTTP in terms of security is idiotic.

    --
    Thank you, Edward Snowden.

    "Arguments from authority are worthless." —Carl Sagan
  3. Re:AdSense supports HTTPS by tlhIngan · · Score: 3, Insightful

    Then use the ads that Google serves. A month ago, Google announced HTTPS support for AdSense.

    And yet, Google doesn't roll out HTTPS support for the rest of the ad companies they own? You'd think if they can do AdSense, they can do AdMob and DoubleClick and their many other ad platforms they host...

    Given Google serves like 98% of the ads on the internet (through AdSense, DoubleClick and other companies), it seems Google's the one holding HTTPS everywhere...