We started getting these errors when searching for packages in ERM eHoldings: [2025/10/30 14:18:08] [WARN] ERROR - EBSCO API /packages?orderby=packagename&offset=1&count=1 returned 400 - The value 'application/json; charset=UTF-8' is not valid for the 'contenttype' parameter. Allowed values: {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, all, aggregatedfulltext, abstractandindex, ebook, ejournal, print, unknown, onlinereference, streamingmedia, mixedcontent}. [2025/10/30 14:18:08] [ERROR] GET /api/v1/erm/eholdings/ebsco/packages: unhandled exception (Mojo::Exception)<<ERROR requesting EBSCO API /packages?orderby=packagename&offset=1&count=1 code 400: The value 'application/json; charset=UTF-8' is not valid for the 'contenttype' parameter. Allowed values: {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, all, aggregatedfulltext, abstractandindex, ebook, ejournal, print, unknown, onlinereference, streamingmedia, mixedcontent}.>> Reverting bug 33481 appears to prevent this from happening. But this looks weird, there seems to be something happening with contenttype vs content-type in the request.
Reverting bug 33481 appears to cause things to go wrong with selecting and deselecting titles and packages so a proper fix is required here.
The error does not mean anything, why are they using the content-type header as a parameter? The doc: https://developer.ebsco.com/knowledge-services/reference/findpackagesbynameusingget there is indeed a contenttype parameter I would contact them and ask what changed and if this behaviour is the expected one, maybe it's a bug on their side.
Created attachment 188926 [details] [review] Bug 41143: Do not include content-type header when searching packages
This patch fixes the problem if you need a hotfix.