Recent updates to some browsers have made them very sensitive to how our proxy server was set up. We believe that we have now configured the server correctly. However, old settings on the web sometimes persist and identify the server as incorrectly configured. We believe that if you clear your browser's cache, the problem will be fixed. The instructions for clearing your cache in Chrome are here. The instructions for clearing your cache in Firefox are here. The instructions for clearing your cache in Safari are here. If the problem persists, please get in touch with Brandon University Helpdesk at email@example.com.
Currently, our One Stop Search service does not insert a link to our proxy server into the links to ProQuest Dissertation and Theses, so that when you click on a link to a thesis in that collection if you are off campus you will be asked to pay for access. We apologize for this. Ex Libris, the software provider for our One Stop Search service, is working on a fix for this. In the meantime, you can log into ProQuest Dissertation and Theses from our databases page where you will be directed to our proxy server and given access from off campus. This is a more awkward way to find the material, and it means you must search for the thesis again, but you will have access to the thesis.
The One Stop Search is on a secure socket layer (i.e. it uses https rather than http). Anytime the One Stop Search calls data from a web site that is not on a secure socket layer, the browser may interpret that call as unsecure and block it. This means that sometimes an attempt to open a full text resource in the One Stop Search page fails unless the user specifically allows it, and depending on the browser, this may not be easy to see. Actually, it may be quite hard. We are working to make our access to resources through the secure socket layer so this won't be a problem. In the meantime, each browser has a different method of allowing you to reach "unsecure" sites.
This is actually long-term known problem for Safari browsers. It’s not major, but it will likely be annoying from time to time. We are hopeful that Safari will find a workaround for this the way that Chrome's Incognito mode has.