In order to provide access to resources that use https, your EZproxy server must be configured with an SSL certificate.
Option CookiePassThrough Cookie wp_ezproxy=1; domain=.washingtonpost.com; path=/; AnonymousURL https://js.washingtonpost.com/* AnonymousURL https://api.washingtonpost.com/* AnonymousURL -re https://[^/]+\.wpdigital\.net/.* AnonymousURL https://video-api.washingtonpost.com/* Title The Washington Post (updated 20210805) U https://www.washingtonpost.com HJ https://www.washingtonpost.com HJ https://subscribe.washingtonpost.com HJ https://account.washingtonpost.com HJ https://smetrics.washingtonpost.com HJ https://sitesearchapp.washingtonpost.com HJ https://cdn-api.arcpublishing.com HJ https://www.washingtonpost.com DJ https://www.washingtonpost.com DJ wpdigital.net Find "www.washingtonpost.com" Replace "^swww.washingtonpost.com^" Find "// Replace "https:// AnonymousURL -* 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: