3 ms·
> you maybe found out about http basic auth, but then you noticed that it's not so convenient to use with mpv Feels exactly as convenient as this method. Set t
by bhaney 2y ago
> you maybe found out about http basic auth, but then you noticed that it's not so convenient to use with mpv
Feels exactly as convenient as this method. Set the Authorization header using mpv's http-header-fields setting to your basic auth creds instead of shoving a PSK in the user-agent setting (and rigging up custom server-side auth to go with it).
But both methods kinda suck if you don't want to be leaking your auth creds to every unrelated http server you play videos from. Is putting the basic auth creds in the url that big of a deal?
- x0777777 2y agoyou are right, I also came to the same conclusion just moments ago after re-evaluating this idea. I still think it is a little more convenient for private use than modifying the url everytime before I can request a certain resource. maybe a more valid idea would be to use seperate configs or profiles in mpv for seperate use cases. thank you for your thoughts, highly appreciated
- bhaney 2y ago> maybe a more valid idea would be to use seperate configs or profiles in mpv for seperate use cases I think that's the way to go. However you choose to pass the auth creds (I would still suggest standard basic auth in http-header-fields), it should be in a profile that can be automatically activated with a profile-cond setting containing a string.match on the path to check for a certain domain name.