Q. Google Chrome and secure access to websites
Due to a Google Chrome update that will occur on Friday 19th June, you may begin to find that some websites you access from the Library website, including the eResources pages, Summon, Library Catalogue, AskUs, etc. may warn you that the site you are about to access may not be secure or is having some other problem.
Please rest assured, that if the URL of the site contains ipacez.nd.edu.au within it, or the Library has linked to it, then we would encourage you to proceed to the site.
If your browser does not allow you to do this, then please either try to access the site via another browser (Firefox, Safari), and/or clear your browser cache and try again.
This change is not only regarding Notre Dame resources, but is being rolled out world-wide, so you may experience the same warning notices from Google Chrome across other websites you access outside of Notre Dame.
If you are trying to access a website that has been linked to from a Notre Dame Library website, and the website is not working, please let us know via the following Report a Problem webform.
Google Chrome Security Blog quote:
"Today we’re announcing that Chrome will gradually ensure that secure (HTTPS) pages only download secure files. In a series of steps outlined below, we’ll start blocking "mixed content downloads" (non-HTTPS downloads started on secure pages). This move follows a plan we announced last year to start blocking all insecure subresources on secure pages.
Starting in Chrome 82 (to be released April 2020), Chrome will gradually start warning on, and later blocking, these mixed content downloads. File types that pose the most risk to users (e.g., executables) will be impacted first, with subsequent releases covering more file types. This gradual rollout is designed to mitigate the worst risks quickly, provide developers an opportunity to update sites, and minimize how many warnings Chrome users have to see."
For more information, please view the full blog post from Google Chrome.