Hi,
I've noticed that Cobalt and Emerald still uses non ssl urls in a site with ssl ( https://mysite.com )
This causes unpredictable behavior when clicking on some links generated by Cobalt and Emerald.
For example if I edit a record and I click on a link of an Emerald protected field, I am logged out automatically.
Another problem is that it causes the browser to block insecure content because of the mixture of secure and non-secure urls in the code.
One solution is to use a component like NoNumber ReReplacer to replace all http:// into https:// or ://
It would be better however to use relative links (://) instead of absolute links (http://) in the code
Best regards,
Jeff
Problem
Announcement
Conversation
Idea
Praise
Question
Open
Hi,
I've noticed that Cobalt and Emerald still uses non ssl urls in a site with ssl ( https://mysite.com )
This causes unpredictable behavior when clicking on some links generated by Cobalt and Emerald.
For example if I edit a record and I click on a link of an Emerald protected field, I am logged out automatically.
Another problem is that it causes the browser to block insecure content because of the mixture of secure and non-secure urls in the code.
One solution is to use a component like NoNumber ReReplacer to replace all http:// into https:// or ://
It would be better however to use relative links (://) instead of absolute links (http://) in the code
Best regards,
Jeff