In order to provide access to resources that use https, your EZproxy server must be configured with an SSL certificate.
This page describes how to configure EZproxy to work with the web-based versions of SciFinder and/or SciFinder-n.
Note: If you provide access to both SciFinder and SciFinder-n, then two starting URL's will be needed on your institution's site. To set a starting URL on your institution's site to SciFinder-n, replace the full URL after the EZproxy prefix for your institution with the host line: https://scifinder-n.cas.org/.
Option X-Forwarded-For Title SciFinder (updated 20210804) HTTPMethod PUT HTTPHeader x-cas* HTTPHeader -request -process x-cas* HTTPHeader X-PatSnap-Version HTTPHeader X-API-Version HTTPHeader X-PatSnap-From URL https://scifinder.cas.org/ H https://scifinder-n.cas.org/ H https://origin-scifinder.cas.org/ H scifinder.cas.org H scifinder-n.cas.org H origin-scifinder.cas.org H https://sso.cas.org H sso.cas.org H chemport.cas.org H chemport-n.cas.org H content2.cas.org D cas.org Option NoX-Forwarded-For
Note: A setting that should not be used in the configuration settings is "DJ cas.org" because it is known to cause "HTTP 500 Internal Server Error" on IE and "500: Server Error" on Firefox during the SciFinder login process.
If you are having problems accessing this resource with your instance of EZproxy, try upgrading to the newest version of EZproxy.
A Hosted EZproxy Include File is available for this resource. Hosted EZproxy customers will receive automatic updates with OCLC’s latest version of this stanza. Note: Hosted EZproxy customers in the Americas using self-service may reference the Include File by adding the following line to config.txt: