How to disable Tracking Logo in Community Edition 201901 GA (Docker)

[r_aurelian]

Hello!

I have installed Alfresco Community Edition 201901 GA (via Docker) and are serving it over SSL using HAproxy reverse proxy. However, my page does not show as secure - the browser complains I have insecure content on my page. The culprit is "http://www.alfresco.com/assets/images/logos/community-5.2-share.png" which is being loaded, but I do not know by what.

How can I disable this? I would not mind the tracking, but the problem is that it`s preventing me from having the page shown as secure.

Setting heartbeat.enabled=false does not have any effect.

Can anyone help?

[jbrasil]

Hello joseantonionava,
Would you have the MessagesWebScript.class file with this change?
Thanks a lot!
Zé Brasil

[joseantonionava · Accepted solution]

Hello jbrasil... sure...

Here you are...

https://mega.nz/#!H4N1QYIB!yajjCVMUAXFZm-sU0fUsJ1OLFmbCWElSJfsoyrWU0_8

First backup the original file... and tell me if it works for you.

Regards.

[jbrasil]

Hi joseantonionava,
It worked.
Thanks a lot for the help.
With best regards,
Zé Brasil

[r_aurelian]

Thank you joseantonionava,

The file worked fine. Hopefully this issue will be actually fixed for good in a future version.

[zerros]

Hello,

How apply this patch in a docker environment please ? I have the same issue with mixed content due to logo.

Thanks.

[michaelzietlow]

I can confirm the 5.2 tracking logo GET, is STILL PRESENT in Community7.0 MessagesWebScript.class 

community7.0# strings /var/opt/alfresco/tomcat/webapps/share/WEB-INF/classes/org/alfresco/web/scripts/MessagesWebScript.class| grep png

j://www.alfresco.com/assets/images/logos/community-5.2-share.png" alt="*" style="display:none"/>'}, 100);

As written this breaks my HAPROXY to NGINX over SSL deployment without running the modified class file listed above. 

Even though I'm running https:// with Nginx, tomcat doesn't know this.

Maybe there is some global properties switch that instructs tomcat to only offer https://  responses?

Otherwise reverse Proxy users may hav to set up ssl certificates on Tomcat and double encrypt.  This way I believe Tomcat will tell all its clients to use https://