search

datarhei / core

datarhei Core is management for FFmpeg processes without development effort. Whether your streaming has one viewer or a million, we have the tools to help you develop, deploy and manage any video project at any stage. We've solved the challenging problems so you can focus on your application, not your infrastructure.
https://docs.datarhei.com/core
Apache License 2.0
180 stars 41 forks source link

hls publication #18

Open furianin opened 5 months ago

furianin commented 5 months ago

Hi,

I noticed that there is a problem in publishing hls to the web server. when I make settings http url protocol specifies where hls should be sent I choose PUT as the method, and I choose delete segments as the hls flag

when I run the publication, I see in the nginx logs that I get code 200, i.e. hls is uploaded to the server and the playlist, while when the delete method comes I get error code 415. (does not delete the hls element) when I try to call curl from my laptop, the hls element disappears from the nginx server without any problems

request for verification.

ioppermann commented 5 months ago

You have to check in nginx that the DELETE is allowed.

For the HLS publication service, we use the HLS output of ffmpeg. The error 415 indicates that nginx has some issues with the provided content type or encoding of the DELETE request: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/415

furianin commented 5 months ago

My nginx understands the delete method. Because when it calls curl in the example: curl -X DELETE http://10.255.5.13/hls/channel2442850.ts This example causes it to remove this file from nginx

The problem is when he publishes the restream and does not delete it.