Announcement

Collapse
No announcement yet.

HTTPS Is Now Enabled For OpenBenchmarking.org Embedded Graphics

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • HTTPS Is Now Enabled For OpenBenchmarking.org Embedded Graphics

    Phoronix: HTTPS Is Now Enabled For OpenBenchmarking.org Embedded Graphics

    For those viewing the HTTPS version of Phoronix, the embedded Phoronix performance result graphs embedded from OpenBenchmarking.org will now work...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Why? Was anyone concerned 3rd parties will know which benchmarks are we looking at?
    At the same time, by increasing the load on your CPUs, you've just got yourself a higher electricity bill.

    Comment


    • #3
      Originally posted by bug77 View Post
      Why? Was anyone concerned 3rd parties will know which benchmarks are we looking at?
      At the same time, by increasing the load on your CPUs, you've just got yourself a higher electricity bill.
      There's a login, so there's a username and a password to input.
      That's worth protecting.

      Besides, it's a tech site, and the current trend is "encrypt everything".
      The additional CPU load is minimal.
      Myth #7 – HTTPS Never Caches People often claim that HTTPS content is never cached by the browser; perhaps because that seems like a sensible idea in terms of security. In reality, HTTPS caching is controllable with response headers just like HTTP.

      Comment


      • #4
        Originally posted by bug77 View Post
        Why? Was anyone concerned 3rd parties will know which benchmarks are we looking at?

        No idea, just what many people have been requesting....
        Michael Larabel
        https://www.michaellarabel.com/

        Comment


        • #5
          Originally posted by The 11th plague View Post

          There's a login, so there's a username and a password to input.
          That's worth protecting.
          Except the article says it's about embedded graphics.

          Originally posted by The 11th plague View Post
          Besides, it's a tech site, and the current trend is "encrypt everything".
          The additional CPU load is minimal.
          http://blog.httpwatch.com/2011/01/28...s-about-https/
          The additional CPU load is minimal because serving http(s) is not particularly CPU-intensive. However, under heavy load/stress, that "minimal" adds up. Or it adds up if you start encrypting left and right, without regard to the sensitivity of the encrypted content. Though it's entirely possible Openbenchmarking.org doesn't see enough traffic to trigger the problem. But one day Michael will post a benchmark that will be so hot, everyone on the Internet will want to see it. Guess who'll be laughing then?

          Comment


          • #6
            Originally posted by bug77 View Post
            The additional CPU load is minimal because serving http(s) is not particularly CPU-intensive. However, under heavy load/stress, that "minimal" adds up. Or it adds up if you start encrypting left and right, without regard to the sensitivity of the encrypted content. Though it's entirely possible Openbenchmarking.org doesn't see enough traffic to trigger the problem. But one day Michael will post a benchmark that will be so hot, everyone on the Internet will want to see it. Guess who'll be laughing then?
            Actually in terms of raw traffic, OpenBenchmarking.org gets even more than Phoronix.com, due to those interacting with it through the Phoronix Test Suite, etc. I wrote an article before how some months NVIDIA alone pulls like 40GB+ down from OB in a month.
            Michael Larabel
            https://www.michaellarabel.com/

            Comment


            • #7
              Thank god, finally.

              Since I'm using HTTPS everywhere, I've had to click the "load unsafe resources" button every time i loaded a benchmarking article. Thanks for fixing this.

              Comment


              • #8
                Originally posted by johanb View Post
                Thank god, finally.

                Since I'm using HTTPS everywhere, I've had to click the "load unsafe resources" button every time i loaded a benchmarking article. Thanks for fixing this.
                Actually, it still isn't fixed. Looking at e.g. https://www.phoronix.com/scan.php?pa...5c-linux&num=3 still doesn't load the images.

                Michael, if you could be so kind, can you make articles default to loading resources from OB over https? Or at least if the article is loaded via https? Browsers are still blocking the mixed content.

                edit: correction, the images actually are loading in Chromium, but without the associated JS for formatting. Firefox doesn't load the images at all.

                edit 2: Now it's working fine on Firefox? I give up.
                Last edited by tga.d; 21 July 2015, 05:20 PM.

                Comment


                • #9
                  Originally posted by tga.d View Post

                  Actually, it still isn't fixed. Looking at e.g. https://www.phoronix.com/scan.php?pa...5c-linux&num=3 still doesn't load the images.

                  Michael, if you could be so kind, can you make articles default to loading resources from OB over https? Or at least if the article is loaded via https? Browsers are still blocking the mixed content.
                  There was another issue within the embed code, should be fixed up now for using HTTPS there.
                  Michael Larabel
                  https://www.michaellarabel.com/

                  Comment


                  • #10
                    Originally posted by Michael View Post

                    There was another issue within the embed code, should be fixed up now for using HTTPS there.
                    Ah, cool. Thanks, that was a faster fix than I was expecting.

                    Comment

                    Working...
                    X