Prutha Kulkarni (Inactive) added a comment - 23/Jul/20 5:53 PM - edited Findings: When I tried to replicate the issue using the link "https://apps.bioviz.org/apps/org.lorainelab.igb.protannot". The console was showing errors and warning which was because of the mixed content i.e. we are trying to access the endpoint from a "https" enabled webpage which is server over "http". The issue is not seen on chrome and Firefox as the mixed content is allowed on these browser. To know more about what mixed content is you can read following article: https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content Since safari 9.1 version release, as per the strict policies the mixed content access is disabled on the browser. There isn't any settings to allow such content on safari now but we can do the same on chrome and Firefox. related links: https://discussions.apple.com/thread/7235380 https://stackoverflow.com/questions/32883306/safari-9-disallowed-running-of-insecure-content As suspected by Dr. [~aloraine] , we might need to shift the rest endpoint to https in order to resolve the issue. We can't resolve it on the browser side and when it comes to the code, it already has CORS settings which could be the potential reason for the same. I even found a link which says safari's updated version doesn't understand "*" the wildcard in CORS settings "Access-Control-Allow-Origin" and that is why the issue occurring. I tried to change the setting on my local IGB version to a known origin url which is "https://apps.bioviz.org/". This worked in Chrome and Firefox again but not in Safari. Then I realized that the browser is blocking the request event before it could reach the api. So I concluded that this won't change anything. Dr. Loraine, could you please let me know your views on this?