You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This happens with a document or the Schema's CSS containing a link to an outside source that required CORS.
We can fix the links on the CSS, but when they come from the document itself, it is out of our control.
Is there a way to mitigate this by providing our own message/popup to explain to people what is going on?
On Mar 29, 2022, at 7:48 PM, Luciano Frizzera ***@***.******@***.***>> wrote:
CAUTION: This email originated from outside of the University of Guelph. Do not click links or open attachments unless you recognize the sender and know the content is safe. If in doubt, forward suspicious emails to ***@***.******@***.***>
This happens with a document or the Schema's CSS containing a link to an outside source that required CORS.
We can fix the links on the CSS, but when they come from the document itself, it is out of our control.
—
Reply to this email directly, view it on GitHub<#60 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAEFJIFGRVERKFM7OIBWPKTVCOJEZANCNFSM42TZK6NA>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
Expected Behaviour
No mixed content warning
Current Behaviour
Browser reports a mixed content warning. Firefox: a yellow caution sign next to the URL
Possible Solution
Change all references in the cwrc-schema template CSS to use
https
instead ofhttp
, for example, https://github.com/cwrc/CWRC-Schema/blob/02c64d48d6786ecf6cbca767919a4064fba06093/templates/css/orlando_v2_cwrc-writer.css#L22The text was updated successfully, but these errors were encountered: