Jump to content

Recommended Posts

Posted

Hi,

 

What is the easiest and most efficient method of forcing to run moodle entirely over SSL https? I've had a search around but haven't really got any definitive answers. Our LEA internet provider is forcing us to have it all over https otherwise they will not allow external access.

 

Running Moodle on Ubunutu Server 8.04 with Apache2 etc...

 

Thanks in advance :)

Posted

Hi thanks for your reply.

 

So far I have it working in as much as I can get to moodle via https://moodle/moodle locally, however all the links/images in moodle are still http, and images etc. How can I change those without hardcoding http--->https?

 

Thanks again

Posted

Actually I have just solved it.

 

In the config.php in the moodle folder I changed

 

$CFG->wwwroot = 'http://moodle/moodle'; to $CFG->wwwroot = 'https://moodle/moodle';

 

Sorted!

 

Cheers

  • Thanks 2
Posted
Glad you got it sorted - we're moving to moodle so I have bookmarked this page just in case I get any problems doing the same thing :cool: lol.
Posted

I'd always thought that I'd setup HTTPS purely for login purposes on Moodle, doesnt HTTPS cause things to slow down a little?

 

I could be wrong....

Posted

Having all traffic subject to HTTPS means that the server has to do an awful lot of calculations for every single request - every page, every CSS file, and every image - for every visitor.

 

The effect this will have will depend on traffic levels and the server specification.

  • 11 months later...
Posted

Hi all,

 

Has anyone else encountered problems with some SCORM content running over a HTTPS connection? Moodle has been running fine here over an fully SSL connection for a while, but we've just tried to install some SCORM course content from Peasons Digital, and it does not run. Pearsons support have simply stated that it is not compatile with HTTPS but without any explanation. We would like to get this working, but would also like to keep using HTTPS... Can anybody help me with this?

 

Thanks in advance,

Tony

Posted
I would suspect that the SCORM content has embedded url referals that are http only. If you have something running on port 80 on the machine (hopefully the webserver, although netcat would be fine I suppose) check what its getting asked for. If this is the case you can fudge the issue with some url rewrite rules.
  • 6 months later...
Posted

I have the same problem with Scorm packages being linked directly to HTTP. I have managed to work around this issue by trying to access the package using Googles chrome browser. When you open the link in Chrome it gives you the true URL to the Scorm package. I have then made a new shortcut/link which contains the corrected URL.

The corrected URL starting with HTTPS not HTTP. This has worked for some Scorm packages.

 

The issue I am having is that some of my packages supplied by AQA have a menu on the right hand side of the (like the old windows explorer view) and each linked document inside that directory tree has its own embedded URL which is HTTP but I cannot find away to create sensible links to this content as there are literally 1000's of different URL's....

 

If anyone has had any success working around this issue I would be very greatful to hear from you.

 

Scorm.png

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...