Skip to main content
  • Subscribe by RSS
  • ExLibris Dev

    Checklist for using https:// in Primo New UI

    • Product: Primo
    • Product Version: November 2016 Release
    • Relevant for Installation Type: Multi-Tenant Direct, Dedicated-Direct, Local, Total Care


    The New UI of Primo was designed from day one to support SSL and https:// out of the box, however despite our best efforts and intentions, occasionally issues arise.

    For example, occasionally a secure (https://) Primo session will request an insecure resource (using http://), causing the content to be blocked by the browser and a mixed content error to be thrown in the Browser's console. 


    The changes necessary to prevent mixed content in SSL mode involve effort both on the Ex Libris side and on the customer side. You will need to verify that a link that was added by the customer can be changed to HTTPS or will open in new window.

    1. Base Urls in Institution Wizard should be converted to use https://.


    2. Template Code urls in Templates mapping table should be converted to use https:// whenever possible, especially for:




    and update the following Template Code urls for 

    amazon_thumb ={{addata/isbn}}.01._SS[size]_SCLZZZZZZZ_.jpg
    PCamazon_thumb ={{addata/isbn}}.01._SS[size]_SCLZZZZZZZ_.jpg


    (be aware of regional variances: na, eu, apac, etc)


    3. Add an institutional row to the URL Attributes mapping table for "OpenInNewWindow" that matches Url Prefix http://.

    (this will cause any remaining links in local or PC records using http:// to open in a new Browser tab, and avoid throwing mixed content errors)


    4. Submit a Case with Primo Support so that settings on Ex Libris side can checked and verified.


    • Article last edited: 05-Feb-2017
    // feedback widged