Why are users proxying to EBSCOhost getting a 400 or 404 error when logging in?
Applies to
- EZproxy
Answer
If users proxying to EBSCOhost get a page giving a 404 or 400 error when trying to login to EBSCO you should first make sure you only have the current EBSCOhost stanza configured. This functionality in EBSCO requires EZproxy the user header X-EBSCO-PROXY-Username. Having anything for EBSCO besides the current stanza can affect this being sent:
https://help-it.oclc.org/Library_Manage...ation_Services
Note the current stanza no longer has the EBSCO LinkSource section at the beginning, make sure that has been removed from your config.txt:
Option DomainCookieOnly
Title -hide EBSCO LinkSource
URL https://linksource.ebsco.com
HJ https://linksource.ebsco.com
HJ linksource.ebsco.com
Once all stanzas for EBSCO except the current EBSCOhost stanza has been removed restart your EZproxy.
Then in your EZproxy admin go to View Server Status and perform the Host Maintenance:
https://help-it.oclc.org/Library_Manage...st_maintenance
Clear out anything shown for orphaned or not used hosts:
Remove X orphaned hosts that have -1 database indexes (requires EZproxy restart)
Remove X hosts that have not been used in over 30 days (requires EZproxy restart)
Then restart EZproxy again.
For stand-alone EZproxy systems, if you need help confirming the user header is being sent contact OCLC Support. OCLC support will require an admin user to access your EZproxy admin page to check on this, as well as your complete config.txt file.
If you are hosted, contact OCLC Support
Additional information
If this error still occurs after confirming the user header is being sent to EBSCO then contact EBSCO support for further assistance.