use browser headers for audiobookbay#52
Merged
Merged
Conversation
This was referenced Jun 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
User-Agentand related browser headers.Why
AudioBookBay was rejecting librarr’s default request identity in this environment. A browser-style request profile is required for the ABB search and detail pages to return usable HTML.
Impact
Validation
go test ./internal/search -run 'TestAudioBookBay|TestResolveABBMagnet|TestRegistryFlow'go test ./internal/searchNotes
This fix is intentionally scoped to AudioBookBay so it does not change the request identity used by the rest of librarr.