warren-bank
commented
3 months ago off-hand, I'd guess that the comment made for major version 2.x regarding the Express.js route is relevant to your usage.. since smth/ are all valid base64 characters.. and by inserting - (or any other character that isn't valid for base64 encoding) would cause the path up to and including the directory containing this invalid character to be excluded.. and the base64 string would begin following the next / character.
note: using v3.x with Express.js can workaround this limitation.
aside: using a URL-safe base64 charset would've made life simpler.. hindsight; I'm probably locked in at this point.
Based on https://github.com/warren-bank/HLS-Proxy/issues/37#issuecomment-1808952022.
How to reproduce:
hlsd -v 3 --host "example.com:443" --port 8080http://localhost:8080/smth/{base64}.m3u8Actual result: 400 bad request
Expected result: HLS file with links containing
https://example.com:443/smth/....However, if you make request with dash inside the URL path prefix, for example
http://localhost:8080/smt-h/{base64}.m3u8, it works as expected