Error message when going to AidView through https

[siwhitehouse]

Hi there

I've had a couple of reports from colleagues over recent weeks that they have received the error shown below

I can replicate it on my machine (Windows 7) using Chrome, with similar errors showing in FireFox and Internet Explorer. I don't get that error if I go to http://www.aidview.net, but I replicate it at https://aidview.net.

Is this a quick fix? We're going live on Thursday!

Oh!

http://grab.by/lE9u (you need to visit the https://aidvidew.net, if that
helps you replicate)

Looks like a certificate mismatch (*.heroku.com -> *.aidview)

I guess the choices are:

• redirect the user back to the http: site
• enable the custom-domain ssl -
  https://devcenter.heroku.com/articles/ssl#customdomain-ssl

redirecting the user would be a small code change (though I'm not totally
sure when I'd get the chance to do this).

Ben

On Mon, Apr 15, 2013 at 3:52 PM, Simon Whitehouse
notifications@github.comwrote:

Hi there

I've had a couple of reports from colleagues over recent weeks that they
have received the error shown below

[image: aidview warning Apr 2013]https://f.cloud.github.com/assets/1718090/381243/7d6cf56a-a5db-11e2-9d3e-e5ecf34cd15b.JPG

I can replicate it on my machine (Windows 7) using Chrome, with similar
errors showing in FireFox and Internet Explorer. I don't get that error if
I go to http://www.aidview.net, but I replicate it at https://aidview.net.

Is this a quick fix? We're going live on Thursday!

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/73
.

[siwhitehouse]

Hi Ben

I was hoping this might be a reasonably simple fix. I don't really have the technical nous to make a decision about what would be best to do here. I'll ask David to take a look and give his opinion.

In the meantime could you check when you might be able to do this for us, please? I'm aware we're outside the window we set for bug fixing.

[siwhitehouse]

Hi Ben

The general consensus is that we don't really need an https endpoint. So, can we go with the redirecting the user option please?

[benfoxall]

just looked into this, the redirect actually won't work (because the request wouldn't be trusted in the first place)

[Mattdevinit]

thanks - is there another simple way of avoiding people getting this warning message?