Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

in HLS, query parameters are not propagated to playlists and segments #3275

Closed
1 of 13 tasks
aler9 opened this issue Apr 20, 2024 · 1 comment · Fixed by bluenviron/gohlslib#165
Closed
1 of 13 tasks
Labels
bug Something isn't working hls

Comments

@aler9
Copy link
Member

aler9 commented Apr 20, 2024

Which version are you using?

v1.6.0

Which operating system are you using?

  • Linux amd64 standard
  • Linux amd64 Docker
  • Linux arm64 standard
  • Linux arm64 Docker
  • Linux arm7 standard
  • Linux arm7 Docker
  • Linux arm6 standard
  • Linux arm6 Docker
  • Windows amd64 standard
  • Windows amd64 Docker (WSL backend)
  • macOS amd64 standard
  • macOS amd64 Docker
  • Other (please describe)

Describe the issue

When a HLS page is requested with query parameters, i.e.

http://localhost:8888/mystream?key=val

The query parameters are correctly propagated to the multivariant playlist (index.m3u8):

http://localhost:8888/mystream/index.m3u8?key=val

But they are not propagated to the media playlist (stream.m3u8) or to segments:

http://localhost:8888/stream/stream.m3u8
http://localhost:8888/stream/seg1.mp4

Describe how to replicate the issue

  1. start the server
  2. publish a stream
  3. open http://localhost:8888/mystream?key=val and follow the process

Did you attach the server logs?

no

Did you attach a network dump?

no

@aler9 aler9 added bug Something isn't working hls labels Apr 20, 2024
@mevoronin
Copy link

Hi. I encountered the same problem.
When using authorization, the server receives a parameter without parameters.
{User="", Password="", Ip="89.221.63.64", Action="read", Protocol="hls", Id=null, Query="_HLS_msn=342&_HLS_part=9&_HLS_skip=YES", Path="e588e1ff-c3cc-4d9c-be38-66106ba4155c"}
It is impossible to authorize such a request.
For HLS, I always made the response 200, but each segment request leads to an authorization request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working hls
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants