Share over SSL alert in Internet Explorer

[aheaven]

Hi !

   I added a SSL connector on port 443 in Tomcat, and now I am accessing Share in https without any problem except for a warning in Internet Explorer that says that I have secured and non-secured content… I get that in any page even after removing the Alfresco Network dashlet that causes the same warning in Firefox…

   Do you know what does that ? Is there any settings I should change ?

   Thanks for your help !

Steve

[rbowman]

Hey guys,

I'm having this same issue (secure/non-secure items pop-up in IE).  I have noticed that the nightly builds are now for 3.2 preview.  Where can I get an updated version of the alfresco-web-framework.jar?  Do I need to do anything else to get rid of the pop-up alert?

I am currently running the latest stable version of alfresco labs on OpenSuSE 10.3/MySQL.  I am handling the SSL connections with apache.

I did try the alfresco-web-framework.jar from the 3.2 preview nightly builds, and it didn't work (as expected).  Crashed the whole application looking for a slingshot template that does not exist in the latest stable version.

Thanks,
-Roger Bowman

[sylvain_d]

Hi !

I finally succeed. I've taken the source from the svn and compiled my own MessagesWebScript.class before put it in the web-inf/… Share folder to overide the one from the jar.

I deleted the line that refer to http://alfresco……

[rbowman]

I believe I have a solution as well.  What I have done is downloaded the 3.2 preview files.  I then grabbed the MessagesWebScript.class file from the 3.2 preview version and added it to the 3 final version alfresco-web-framework.jar.  This has gotten rid of the "Secure and Non Secure" items popup window from IE and seems to have not broken anything else in the process.  Hope this helps someone!

Just out of curiosity, why didn't this get back-ported to version 3.0 final?

Thanks,
-Roger

[mikeh]

Just out of curiosity, why didn't this get back-ported to version 3.0 final?

We only tend to back-port critical bugs, i.e. those that could result in data loss or significantly reduced functionality.

The other reason could be that this was never raised as a bug in JIRA.

Thanks,
Mike