EBSCOhost
Versions of EZproxy prior to 2.4b
are producing the error
"Application Level Exception" when used to access the August 2007
version of EBSCOhost. If your institution is encountering this
error, please see Which Version of EZproxy is on my Server? for
information on how to check the version of EZproxy you are using
and Download to find information on how to perform
a no cost update to the current release.
EBSCO's Visual Search requires EZproxy 3.6c GA (2006-03-10) or later.
EBSCOhost requires the following configuration:
Title EBSCOhost
URL http://search.ebscohost.com/login.aspx
DJ ebscohost.com
Host search.epnet.com
DJ epnet.com
Host openurl.ebscohost.com
Find proxy.cfm?url=http://
Replace proxy.cfm?url=http://^A
Find /login?url=http://
Replace /login?url=http://^A
As of July 1, 2007, EBSCO has phased out the use of the epnet.com domain.
Any existing URLs with epnet.com should be changed to use ebscohost.com instead (e.g. search.epnet.com becomes search.ebscohost.com).
The "Host search.epnet.com" line was returned to the recommended
configuration, though, since the EBSCOhost XML search
interface currently
returns URLs with this hostname, which can cause select federated search
solutions to also return URLs with this hostname. There were also reports
of other epnet.com (e.g. therapy.epnet.com) still using the old name,
so "DJ epnet.com" has also been restored to the recommended configuration.
The first Find/Replace is required if you use RefWorks to insure that citation
exporting to RefWorks will work correctly.
The second Find/Replace works with the EBSCOhost administrative Setup/Maintain
Proxies option where you can provide a Proxy URL Mask to point have
persistent links pointed back to your EZproxy server. These lines help
prevent the persistent URL from being rewritten, avoiding URLs that look like
http://ezproxy.yourlib.org/login?url=http://search.ebscohost.com.ezproxy.yourlib.org/.
If you use EBSCO LinkSource, you should also review
EBSCO LinkSource .
EBSCO A-to-Z and EBSCO EJS
EBSCO A-to-Z and EBSCO EJS are completely separate products
from EBSCOhost. Useful Utilities does not have access
to the information required to prepare a comprehensive definition
for these resources. EBSCO does provide a configuration for EJS
upon request.
Common cause of "Page not found" errors after updating this definition
Please note that EBSCO migrated from the use of hostnames ending
in epnet.com to hostnames ending in ebscohost.com over the summer of 2006.
During this migration, many new web servers will be proxied. Useful Utilities
anticipates that this change will trigger page not found errors related to
Troubleshooting Common Problems
under "1.a. Proxy by port has worked for awhile, but gives this error to all remote users for certain databases, particularly new databases." If you see this error, particularly if you use proxy by port, please refer to this page
regarding a common firewall issue that can cause this behavior and how to
correct it.