Lab status page broken if used with https

[LOZORD]

https://uw-upl.github.io/#/lab

Here's the error message:

Mixed Content: The page at 'https://uw-upl.github.io/#/lab' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://eris.upl.cs.wisc.edu:1312/lab-status'. This request has been blocked; the content must be served over HTTPS.

So basically, do we want to add https to eris?

[Squeakrats]

Uh the URL in code can prob just have an s added to it.

[LOZORD]

@Squeakrats do you mind taking care of it?

[Squeakrats]

I'll try

[LOZORD]

🐫

[spwilson2]

🐫

[Squeakrats]

Oh yea I forgot about this. I believe the issue was that I needed to create an Https Cert? I probably should know this but does anyone know if thats how that works? Im pretty sure the issue was https pages cant do anything over http (which the lab status was) and to make the lab status https you need https certs.

[Squeakrats]

• I also think adding it is more of a hassle than its worth. Adding https doesn't really get us anything.

[Squeakrats]

Leo would you have a problem with just re-directing https to http?

[spwilson2]

Is there any way we could redirect to an https page that warns about going to unencrypted http beforehand? I reaally don't like the idea of redirecting from https to http - especially without a warning. Although anyone who really cares should just be using https everywhere

[Squeakrats]

Probably. But like what content do we have that would need to be over https?

[spwilson2]

It's mostly about the principle to me, if you really want we can discuss at coord meeting tho

[Squeakrats]

suar

[LOZORD]

Redirecting is a non-optimal solution. Up to you guys.

On Wednesday, June 8, 2016, Squeakrats notifications@github.com wrote:

suar

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#76 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/ADhFUVcsctpcQkIb_u0UrzVAmbBia6Hsks5qJh2OgaJpZM4HwRoZ
.

[LOZORD]

FYI: https://github.com/blog/2186-https-for-github-pages

On Wednesday, June 8, 2016, Leo Rudberg ljrudberg@gmail.com wrote:

Redirecting is a non-optimal solution. Up to you guys.

On Wednesday, June 8, 2016, Squeakrats <notifications@github.com
javascript:_e(%7B%7D,'cvml','notifications@github.com');> wrote:

suar

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#76 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/ADhFUVcsctpcQkIb_u0UrzVAmbBia6Hsks5qJh2OgaJpZM4HwRoZ
.

[spwilson2]

As far as I know the problem isn't on the github side, but on the eris
side. Github HTTPS is working fine it's the trying to get lab status from
eris over HTTPS that's the issue. (I think)
On Jun 8, 2016 3:37 PM, "Leo Rudberg" notifications@github.com wrote:

FYI: https://github.com/blog/2186-https-for-github-pages

On Wednesday, June 8, 2016, Leo Rudberg ljrudberg@gmail.com wrote:

Redirecting is a non-optimal solution. Up to you guys.

On Wednesday, June 8, 2016, Squeakrats <notifications@github.com
javascript:_e(%7B%7D,'cvml','notifications@github.com');> wrote:

suar

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<
#76 (comment)
,
or mute the thread
<
https://github.com/notifications/unsubscribe/ADhFUVcsctpcQkIb_u0UrzVAmbBia6Hsks5qJh2OgaJpZM4HwRoZ

.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#76 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AK9rOMJdHQmnR0OPSRPAvrSO4fMl8HjZks5qJygfgaJpZM4HwRoZ
.

[Squeakrats]

Yup I believe so too.

[WowSuchRicky]

Merging with #110 .