api/bilibili: fetch playinfo from their api - #1551
Open
zImPatrick wants to merge 1 commit into
Open
Conversation
lambovl
pushed a commit
to lambovl/cobalt-WSS
that referenced
this pull request
Aug 27, 2026
cherry-picked from upstream PR imputnet#1551 by @zImPatrick (preferred over PR imputnet#1575, which replaces html parsing entirely, caps quality at qn=64 and carries unrelated vite.config changes)
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
1 participant
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.
Bilibili downloading broke a few days ago because they just stopped returning
__playinfo__for some requests?Getting the aid (video id), cid (channel id..?) and bvid (this one isn't actually required but why not) and sending those to the endpoint the site uses when it has no playinfo seems to work just fine
The only thing that matters when calling that endpoint is the
Refererheader, otherwise you don't get a successful responseShould fix #1545