Forum Discussion

RickyFowler-0ed's avatar
RickyFowler-0ed
Community Member
10 months ago

"http" versus "https"

We received notice from our IT Department that we now have to change all our course links from "http" to "https." This impacts both the front and back end of our courses. On the front end our learners access the courses through the learning management system. On the back end the learner rosters their course completion. 

The problem is the "http" links work, but when we change the links to "https" they don't work. We are also curious how this impacts the way we publish our courses, as our links point to the html.story file produced when publishing.

Thank you,

 

Ricky Fowler

  • The  “s” in “https” refers to how the server handles security. So you may have to change the address of the LMS, but it should access courses that are uploaded to it.   If not, sit down with IT for a face to face. It sounds like you got an automated notification. Make sure they have implemented it, and why “http” works and “https” doesn’t.

    The .html file that is produced by publishing doesn’t enter into the equation, so it doesn’t need to be changed.  http://company.com/file.html and https://company.com/file.html are the same file, just think of them as living at different addresses.

  • is there any way to publish only for https? I have many users who receive browser errors (we are using chrome) because the content is unsecure and wont launch until you update the browser to say allow. To the above point our LMS vendor indicated the only permanent fix is to update the LMS web address to HTTPS but was curious is there anything we can do while publishing courses as a work around.

  • the admin of your LMS (-> web server) can solve the problem -> always redirect http to https

    (all websites that I know do this)