Spaces in #EXT-X-KEY/URI fail with PKCS#5:unpad error
Nobody has claimed this yet.
- Dominant language
- ActionScript
- Stars
- 744
- Forks
- 259
- PR merge metrics
- No merged PRs in 30d
Description
If URI in:
EXT-X-KEY:METHOD=AES-128,URI=".."
contains non-url encoded characters, such as spaces the plugin with throw PKCS#5:unpad error. This is tested with StrobeMediaPlayback.
Unfortunately, the platform we are using does not url encode the KEY URI. If this lack of url encoding is the problem, can you consider adding url encoding of the uri stem between the "/" characters as a defensive measure?
sample m3u8:
http://174.37.213.54/dptek/_defnst_/mp4:hlstest/path%20has%20space/debug.mp4/playlist.m3u8
Thank you!
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 reproducing the failure with the sample m3u8 playlist and the StrobeMediaPlayback setup, then trace handling of the EXT-X-KEY URI before PKCS#5 unpadding. Done means a key URI containing spaces is handled without the PKCS#5:unpad error while existing HLS playback continues to work.
Written by the indexing model from the issue text.
Assessment
- Domain
- audio-video-rtc
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100