Closed rluetzner closed 2 months ago
Huh, interesting. According to the OPDS specs, the query
parameter should actually be called q
instead.
https://specs.opds.io/opds-1.2#3-search
Here are some example searches.
With such a template, an OPDS Client could for example support the following search queries:
http://example.com/search?q=gardening http://example.com/search?q=gardening&author=smith http://example.com/search?author=drucker http://example.com/search?author=ferriss&title=four
The best defensive option would be to look for either q
or query
in the request. I'll see if I can get this done later.
I noticed the following error when using KOReader to access the OPDS feed.
It shows me the option to search the OPDS library, but fails with an exception in Jellyfin.
According to my reverse proxy, the request looks like this:
405 and 400 are the return codes.
Here's the exception that I get from Jellyfin:
It looks like the query parameter does not have the expected name
searchTerm
. Seeing as KOReader works perfectly well with other OPDS sources, I suspect that it's a bug in this plugin.Thanks for all the hard work. I'll see if I can turn up some more information once I get to a real PC. 🙂