You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
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.
The text was updated successfully, but these errors were encountered: