ClinicalKey and EMBASE

ClinicalKey requires the following database definition in config.txt:

Title ClinicalKey
MimeFilter application/json .* javascript
URL https://www.clinicalkey.com
HJ www.clinicalkey.com
DJ clinicalkey.com
NeverProxy cdn.clinicalkey.com

ClinicalKey Australia requires the following database definition in config.txt:

Title ClinicalKey Australia
MimeFilter application/json .* javascript
URL https://www.clinicalkey.com.au
HJ www.clinicalkey.com.au
DJ clinicalkey.com.au

EMBASE requires the following database definition in config.txt:

Title EMBASE
URL http://www.embase.com/
HJ www.embase.com
DJ embase.com
HJ acw.elsevier.com
NeverProxy static.embase.com

To support the full funcitonality of ClinicalKey within EZproxy, the following lines must be added to the EZproxy config.txt file:

HTTPMethod PUT
HTTPMethod DELETE

These directives are not position dependent, and can be placed anywhere within the config.txt file to affect the ClinicalKey stanza.

Please note: ClinicalKey requires EZProxy 5.7 or above to function properly. ClinicalKey and ClinicalKey Australia require SSL to be enabled. Use the information on OCLC's SSL Configuration page to enable https (SSL) proxying.