Admins: Configuration for basic proxy access

ebrary works well with the following proxy servers when configured properly:

  • EZproxy
  • WAM
  • Squid

Configuration Notes

EZproxy with https URL:  we encourage implementing a security certificate such that https protocol is being used.

Add the following 7 lines to your EZproxy config file
NOTE:  replace XXXXX with your ebrary site name

Option DomainCookieOnly

Title ebrary

URL http://site.ebrary.com/lib/XXXXX

DJ ebrary.com

Find “site.ebrary.com/

Replace “^psite.ebrary.com^/

Option Cookie

Then comment out or remove any previous configs for ebrary and restart your EZproxy server

EZproxy with http URL:

Although not a recommended practice, contact support@ebrary.com if you choose to implement the non-secure http access

Add the following 5 lines to your EZproxy config file
NOTE:  replace XXXXX with your ebrary site name

Title ebrary

URL http://site.ebrary.com/lib/XXXXX

DJ ebrary.com

Find “site.ebrary.com/

Replace “^psite.ebrary.com^/

Then comment out or remove any previous configs for ebrary and restart your EZproxy server

The above EZproxy information is for basic proxy access, if you are instead interested in EZproxy Single Sign On (SSO), see:

http://support.ebrary.com/kb/ezproxy-sso/

WAM proxy:

Contact support@ebrary.com so we can configure for http access

Add this line to your WAM configuration to ensure the links on your ebrary landing page can be used by remote users.   Your WAM foreward table entry should be:

*.ebrary.com

If you don’t use wildcards, you can specify each domain:

corp.ebrary.com

www.ebrary.com

covers.ebrary.com

Squid proxy:

Needs to be set to not cache control