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
Hi, Scott and Greg, I noticed in my latest email alert from Primo production, the links to individual items (articles, books) point to a nonsecure http. So if I click on an item in my alert email, I get a screen like the one below. (Chrome and Firefox on Windows 10) If I then start doing other searches, my activities continue to be "not secure."
Normally if I go to the SoS website from the library home page and do a search, everything including the permalinks are https. Can the links in the emailed alert also be https?
Thanks, Karen
The text was updated successfully, but these errors were encountered:
@kmerguerian can you attach the email you received from alert.
if you hover over links in those emails what do they look like?
I'm looking at other examples of search alerts and all of those links are https://
now some of the records called up show not secure because there are parts of the record that are http and usually not controllable by us -- mostly PCI records in the case of articles.
in which case - the page will alert a user that there is mixed content in the page, but the address is till under https://
Hi, Scott and Greg, I noticed in my latest email alert from Primo production, the links to individual items (articles, books) point to a nonsecure http. So if I click on an item in my alert email, I get a screen like the one below. (Chrome and Firefox on Windows 10) If I then start doing other searches, my activities continue to be "not secure."
Normally if I go to the SoS website from the library home page and do a search, everything including the permalinks are https. Can the links in the emailed alert also be https?
Thanks, Karen

The text was updated successfully, but these errors were encountered: