|
URL Information for Firewall/Proxy Administrators
Ovid recommends that you allow users to connect to all *.ovid.com domains, to ensure uninterrupted access for users.
If that is not possible, we recommend that you allow access to the following service URLs, depending on which products you subscribe to. For optimum performance we recommend you do NOT cache pages originating from the below addresses.
Ovid resource Service URLs:
http://ovidsp.ovid.com
https://ovidsp.ovid.com
http://pt.wkhealth.com
https://pt.wkhealth.com
http://gateway.ovid.com
https://gateway.ovid.com (optional SSL access)
http://ssolver.ovid.com
http://clinicalresource.ovid.com
http://stats.ovid.com
http://linksolver.ovid.com
http://clineguide.ovid.com
http://nursing.ovid.com
These are the only entry-point addresses that should be bookmarked and distributed to users.
http://ovidsp.tx.ovid.com*
http://ovidsp.uk.ovid.com*
*If you wish to bookmark OvidSP, please use http://ovidsp.ovid.com only. Including “tx” or “uk” could compromise your access to OvidSP.
Ovid company Web site:
http://www.ovid.com
Other notes for Network Administrators:
All network traffic from Ovid to the your site should be in response to requests which users have generated. Thus, if your site is using a stateful protocol inspection (SPI) firewall, you should not have to open any ports on your firewall. Email is the exception, and you should allow TCP/25 from the address ranges listed below.
Should you use a non-SPI firewall, you will need to allow ephemeral (high numbered) TCP port access from the following IP address ranges. In order to allow Ovid the ability to expand/upgrade service without impacting connectivity, the entire range should be allowed.
160.109.106.x
160.109.107.x
160.109.108.x
160.109.109.x
160.109.112.x
160.109.113.x
160.109.114.x
160.109.98.x
194.66.22.128/26 (194.66.22.128 - 194.66.22.191)
To avoid problems with email delivery for users of OvidSP’s AutoAlert and email functions, wkhmrmail.ovid.com/160.109.98.52, 194.66.22.174, 194.66.22.175, and should also be explicitly whitelisted.
Last updated 08/09
|
