Curl backend needs a way to force ipv4/ipv6
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 37k
- Forks
- 3.5k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 22
Description
Expected behavior of the wanted feature
The curl backend needs a way to force ipv4/ipv6.
Sometimes, youtube blocks a host's ipv6 address but allows its ipv4 address, or vice versa. We can force yt-dlp to use ipv4 or ipv6 with --ytdl-raw-options and get the stream URLs, but it does not look like there's a way to force a specific stack for the retrieval.
I'm currenty getting 403 errors because while yt-dlp gets the URLs correctly (ipv4), mpv tries to play the content using ipv6.
Alternative behavior of the wanted feature
Some method of forcing ipv4 or ipv6. Maybe even a --curl-raw-options argument.
Log File
No response
Sample Files
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating mpv's curl backend and the retrieval path used after yt-dlp supplies stream URLs. Review how existing raw options are passed, then determine how a user-facing IPv4/IPv6 choice should reach that backend. Done means playback can force either address family without changing the URL-generation behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100