SpringerLink is accessed using the HTTPS protocol for users of Google's Chrome browser or by typing https://link.springer.com into the browser address bar.
If you need any assistance accessing SpringerLink reach out to us by submitting a ticket here: New Support Ticket.
Some steps may need to be taken by site administrators, webmasters, or network support if there are setups that rely on the distinction between HTTP and HTTPS in the URL string. Some cases we've identified are as follows:
- Setup of Proxy Service, such as EZProxy
- Please update your setup so request for an HTTPS link will be routed through your proxy service correctly.
- EZProxy has updated their Stanza to show the HTTPS version OCLC SpringerLink Stanza. If you use a different proxy service please check with their support team for enabling HTTPS access.
- Check out our support article for helpful tips here: Configure a proxy to work with SpringerLink
- Due to a security issue we will be ending support on 31 May 2018 for TLS1.0 and TLS 1.1 and only support TLS 1.2. For more information on the changes to TLS support please refer to the Security Enhancements for Springer Nature Platforms page.
- If you are using version 5.7.44, the last version prior to version 6.x, you will get connection errors as version 5 does not support TLS v1.2. Please contact OCLC and work with them to update to version 6.x. You can find out about the most up to date version of EZProxy on the OCLC Install and Update EZProxy resources page.
- Link Resolvers
- If you use MARC records or KBART files these will still refer to the HTTP version until a time yet to be determined. This should not cause a compatibility issue.
If you have reached this article because you are experiencing a problem that you believe is related to HTTPS please share that problem with us so we can work with you to see that your HTTPS experience is corrected. Or, if you need to report an access issue, please use the Institutional Online Access Issues – Contact Form.
If you are a webmaster or admin we suggest you look at this web.dev page about enabling HTTPS on your servers.