stuck invalidsrc check with streaming responses

[mphilipps]

hi,
I have one server where snallygaster fails to run due to encountering a response of content-type multipart/x-mixed-replace.

Maybe snallygaster should just do a HEAD request or at least have a timeout for invalidsrc requests?

[hannob]

There are some requests that don't limit the retries and I see that this can cause long request times. I don't see an option to set a timeout on poolmanager requests, but I'll look into it.

But in any case: I have no idea how this should depend on the content type. Do you have an example where this appears?

[mphilipps]

https://imker-joellenbeck.de/webcam , but any kind of streaming response would cause that.