Moodle and IE8

[barney]

Apologies in advance if this has been posted before - I did search the forum but can't find a solution!

 

 

Users logging into Moodle using ie8 (it's only ever IE - not any othere browser, surprise surprise ) receive the IE has blocked this website from displaying content with security certificate errors. Click here for options.

 

Tried adding site to Local Intranet but the error persists!

 

Thanks in advance

[SYNACK]

This is not a moodle error but a SSL certificate one, perhaps the certificate is revoked or from a local certificate server.

 

If it is a trusted certificate you can import it to a group policy and push our a trust for it which may help solve the issue.

[barney]

I realise it's a browser issue, in fact an IE issue - it doesn't happen with any other browser. What I don't understand is, if it's an SSL issue why aren't other browsers reporting similiar. Also non of the settings for http security are turned on in Moodle see image, so why is IE looking for certs??? Confused.

[SYNACK]

It is an IE issue in the fact that IE is much more careful with SSL certs than some other browsers. Perhaps there is some linked content like an image from an https link or something. Without way more information and probably screenshots it is all an exercise in guessing though. Is the site externally accessable?

[barney]

I realise it's a browser issue, in fact an IE issue - it doesn't happen with any other browser. What I don't understand is, if it's an SSL issue why aren't other browsers reporting similiar. Also non of the settings for http security are turned on in Moodle see image, so why is IE looking for certs??? Confused.

[ATTACH=CONFIG]11298[/ATTACH]

[barney]

Yes, totally accessible externally and has been for a couple of years. Again, this issue happens with ie 8 and above. Linux, MAC IOS or PC running any other browser report no SSL errors - to me, why would they, we aren't using any????

[SYNACK]

If you actually read my reply above then perhaps you would have seen the bit where I said it may have links to images or scripts that are over an SSL connection. IE8 and IE9 are very good at checking certs and preventing cross site scripting style attacks. This may be why they only show up under IE as it is being more careful, this is not a fault but better security.

 

The reason I asked if it was externally accessable was so that you could post a link to the offending page and maybe someone may have been kind enough to look at it for you and see if they could help you track it down.

 

I hope the repost in #5 was accidental rather than an ignoreing of the reply.

 

The browser is almost certainly not the problem, it is an issue in the site that other browsers have not picked up which never the less should be dealt with.

[barney]

You don't have to patronise me, of course it was a accidental repost and I read your post.

Thanks for your pointers, I need to go through all the links on the homepage (assume it would just the homepage or could it be anywhere???) looking for a https link

[SYNACK]

You don't have to patronise me, of course it was a accidental repost and I read your post.

Thanks for your pointers, I need to go through all the links on the homepage (assume it would just the homepage or could it be anywhere???) looking for a https link

 

It should just be the initial page and any content directly loaded by it or its scripts. The first thing I would try is to view the source of the page and do a search for "https:" which may be able to shine some light on what could be triggering the warning.

[pete]

Using "View Page info" and the web developer tools in Firefox on the offending page(s) should make it obvious where the issue lies.

 

LiveHTTPHeaders is also handy for replaying the browser > server conversation.

[barney]

Thanks to the pair of you! Used the livehttpheader and found our library search block included a link to a https library whose certificate had expired.

 

Thanks agains