mirror of
https://github.com/sigma67/ytmusicapi.git
synced 2026-04-25 15:26:01 +03:00
[PR #394] [CLOSED] Unrecognized case sensitive headers during auth #606
Labels
No labels
a/b
bug
documentation
enhancement
good first issue
help wanted
invalid
pull-request
question
wontfix
yt-error
yt-update
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ytmusicapi#606
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/sigma67/ytmusicapi/pull/394
Author: @czifumasa
Created: 5/18/2023
Status: ❌ Closed
Base:
master← Head:case_sensitive_auth📝 Commits (1)
145bd2dFixed unrecognized case sensitive headers during auth📊 Changes
2 files changed (+2 additions, -2 deletions)
View changed files
📝
ytmusicapi/auth/browser.py(+1 -1)📝
ytmusicapi/auth/oauth.py(+1 -1)📄 Description
Browser authentication doesn't work when I copy request headers from Chrome.
The reason is request headers are Capitalized in Chrome.
From CaseInsensitiveDict docs:
All keys are expected to be strings. The structure remembers the case of the last key to be set, and ``iter(instance)``, ``keys()``, ``items()``, ``iterkeys()``, and ``iteritems()`` will contain case-sensitive keys. However, querying and contains testing is case insensitive::With that in mind I replaced "headers.keys()" method with better check and now check for request headers should be case insensitive.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.