PEP Web

In order to provide access to resources that use https, your EZproxy server must be configured with an SSL certificate.

Option CookiePassThrough
Title PEP (updated 20260929)
HTTPHeader -request -inject PEP-Proxy-Host (server:url:http =~ "@^http://([^:]+)@", re:1)
HTTPHeader -request -process RSC
HTTPHeader -response -process RSC
HTTPHeader -request -process Next-Action
HTTPHeader -response -process Next-Action
HTTPHeader -request -process Next-Url
HTTPHeader -response -process Next-Url
HTTPHeader -request -process Next-Router-*
HTTPHeader -response -process Next-Router-*
HTTPHeader -request -process Origin
HTTPHeader -request -process X-*
HTTPHeader -response -process X-Action-*
HTTPHeader -response -process X-Nextjs-*
HTTPHeader -request -process Access-Control-Request-*
HTTPHeader -response -process Access-Control-*
URL https://pep-web.org
H https://www.pep-web.org
H https://api.pep-web.org
H https://pads.pep-web.org
H www.pep-web.org
H api.pep-web.org
H pads.pep-web.org
D pep-web.org
NeverProxy assets.pep-web.org
NeverProxy cms.pep-web.org
Option Cookie

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:

IncludeFile databases/pepweb.txt