-
-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] OPDS Catalog Fails to Display #513
Comments
Thanks for bringing this to my attention! Unfortunate this slipped through the cracks for a few weeks that it sat in the I've seemingly fixed it locally and pushed the changes up if you look at the linked PR. I've added a debug commit to push a |
I used Image=docker.io/aaronleopold/stump:opds-path-error-patch It seems to work now: |
Awesome! Thanks for validating the image. I'll update this issue once the fix is fully released tomorrow |
Fixes #513 This was a classic instance of organizing the router layers incorrectly, so the API key middleware was being run for both variants of the router instead of just when the `:api-key` path hits a match. This is a pretty large bug that somehow went missed for the 3-4 weeks this sat in the nightly image lol I'll release `0.0.9` as a hotfix ideally tomorrow
The fix is in |
Description of the Bug
Open URL for OPDS. Example: http://10.0.1.4:1801/opds/v1.2/catalog
HTML Response Body Contains Message:
Expected Behavior
Expected catalog content.
To Reproduce
I used
podman
configuration pointing directly to v0.0.8. I added discussion on this topic #512Environment:
Build Details:
Semantic version: v0.0.8
Exact commit: 2c0208c
Build date: December 3, 2024 4:43 PM
The text was updated successfully, but these errors were encountered: