How an Optimizing Compiler Works

Re:How an Optimizing Compiler Works by MauranKilom on Monday November 11, 2019 @02:29PM (#21508009)

The site goes into an endless reload loop when attempting to connect using HTTPS...

[ Parent | on HN ]

Re:How an Optimizing Compiler Works by Sohcahtoa82 on Monday November 11, 2019 @02:36PM (#21508087)

Are you using HTTPS Everywhere or some other similar browser plugin?

When I used HTTPS, the page loaded fine, but then reloaded itself using HTTP, but didn't loop after that.

OP, you may want to look into figuring out why your page reloads using HTTP after loading just fine with HTTPS.

[ Parent | on HN ]

Re:How an Optimizing Compiler Works by yorwba on Monday November 11, 2019 @03:14PM (#21508420)

It's probably due to this script tag:

  <script>if (window.location.protocol == "https:")
    window.location.href = "http:" + window.location.href.substring(window.location.protocol.length);
  </script>

[ Parent | on HN ]

Re:How an Optimizing Compiler Works by notamy on Monday November 11, 2019 @03:23PM (#21508502)

But why? Genuinely curious, is there a real reason why this might be done?

[ Parent | on HN ]

Re:How an Optimizing Compiler Works by lihaoyi on Monday November 11, 2019 @06:44PM (#21510153)

Honestly I do not remember at all why I put in that script tag. It was something to do with github-pages not supporting HTTPS properly in the past, the details escape me. I should probably remove it

[ Parent | on HN ]

Re:How an Optimizing Compiler Works by vbezhenar on Monday November 11, 2019 @06:13PM (#21509941)

May be he hates https :)

[ Parent | on HN ]

Re:How an Optimizing Compiler Works by Sohcahtoa82 on Monday November 11, 2019 @05:41PM (#21509710)

I'm flabbergasted as to why someone would ever think they need to do this.

Especially since the page loads just fine. It's not like it's relying on accessing some 3rd party resource that's only accessible via HTTP.

[ Parent | on HN ]