It looks like for some reason souphttpsrc issues two different types of requests. The first one does a GET on the full URL of the stream with a Keep-Alive header, the second one does a GET on the relative path of the stream only with a close header, and other additional headers such as icy-metadata, transferMode.dlna.org and User-Agent.
The thing is, I have no clue as to why the requests issued are different. Setting GST_DEBUG to souphttpsrc:5 doesn't show any difference in the logs between the two requests (except the response).
It looks like for some reason souphttpsrc issues two different types of requests. The first one does a GET on the full URL of the stream with a Keep-Alive header, the second one does a GET on the relative path of the stream only with a close header, and other additional headers such as icy-metadata, transferMode. dlna.org and User-Agent.
The thing is, I have no clue as to why the requests issued are different. Setting GST_DEBUG to souphttpsrc:5 doesn't show any difference in the logs between the two requests (except the response).