Closed marukka closed 9 months ago
Indeed, the URL parameters should be passed through to the segments requests, but currently are not. Will fix.
This should be fixed in the latest 0.2.11 release; please let me know if not.
If you know of a public MPD that uses this token scheme, that would be useful to add to our test suite.
Thank you so much!
On Sat, Dec 9, 2023 at 7:46 AM Eric Marsden @.***> wrote:
This should be fixed in the latest 0.2.11 release; please let me know if not.
If you know of a public MPD that uses this token scheme, that would be useful to add to our test suite.
— Reply to this email directly, view it on GitHub https://github.com/emarsden/dash-mpd-cli/issues/27#issuecomment-1848414838, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAXMZQ7PEKISOSVEPQ5JAVLYIRTURAVCNFSM6AAAAAA74TFIDWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBYGQYTIOBTHA . You are receiving this because you authored the thread.Message ID: @.***>
I am trying to download .mpd streams which request a token passed as a GET parameter in the HTTP request. As it doesnt seem like this is passing the the GET parameters from the URL I provide the program, any attempts to obtain the .m4s files results in HTTP 401 errors. Is there any way to do this with dash-mpd-cli?