Logging in with HTTPS enabled

Logging in with HTTPS enabled

by Tim Bateson -
Number of replies: 4

Hoping someone can help me here. I am testing a new moodle server running 2.3.2. I have enabled https for logins and all works well within the school.
However, when trying to connect via the internet (Which involves being passed via two ISA servers!) I get the error message shown at the bottom of this post. At first I thought the server was unable to load nay content via https:, but ont manually loading other pages by adding https to the url it loaded fine. In fact if I untick the force logon via https, I can actually login to https://someserver/login/index.php without issue?

Hoping someone can help me with this issue, one though I have had is to change the code for the Login links on the front page to use https rather than http. 

Has anyone else seen this issue?
Can anyone advise on the best way to modify the code so that Login links would https, rather http.

Thanks,

Tim

This web page has a redirect loop

The web page at https://someserver/login/index.php has resulted in too many redirects. Clearing your cookies for this site or allowing third-party cookies may fix the problem. If not, it is possibly a server configuration issue and not a problem with your computer.

Here are some suggestions:

Error 310 (net::ERR_TOO_MANY_REDIRECTS): There were too many redirects.
Average of ratings: -
In reply to Tim Bateson

Re: Logging in with HTTPS enabled

by Tim Bateson -

Sorry to bump this. But, I am still having issues with this. Can anyone offer any suggestions please?

In reply to Tim Bateson

Re: Logging in with HTTPS enabled

by John Gifford -

I don't know if this will be any help but I'm in exactly the same position with the school I work at. We have an LEA ISA server and a TMG server sitting between the outside world and our moodle site, in school the site works just fine (certificate issues notwithstanding), but not outside.

I've looked up this error and one forum reports it could be a time related issue. I know from my viewpoint that the internet time and the time on our server are about 3 minutes out, the server is part of a domain so it needs to have the same time as the PDC; which is about 3 minutes slow.

The problem also appears to only affect Google Chrome as IE 9 doesn't show the same problem, it just won't display the https login page (having just tried a remote login to my home computer). Change the http to https and everything appears to work apart from a constant message about secure and unsecure content (so in chrome stuff like the dock disappears, or in school no theme is applied). I found a line in the config.php file inside moodle $CFG->wwwroot=... where if you change the http:// to https:// everything works, but the drawback is that forces the whole site onto https which can cause content problems as the browser can no longer cache material, on a big site it can cause a really significant slowdown.

Any help with this would be greatly appreciated as I can't see a solution apart from https the whole site.

In reply to John Gifford

Re: Logging in with HTTPS enabled

by John Gifford -

I got it sorted of sorts...

We've now got Apache 2.4 driving the internal LAN access over http while the external facing site is IIS7 with just https. So externally the whole site is https but haven't found any problems so far with content.

Currently working on getting the NTLM SSO part working inside....

In reply to John Gifford

Re: Logging in with HTTPS enabled

by John Gifford -

I got it sorted of sorts...

We've now got Apache 2.4 driving the internal LAN access over http while the external facing site is IIS7 with just https. So externally the whole site is https but haven't found any problems so far with content.

Currently working on getting the NTLM SSO part working inside....