Re: Version 1.4.x opens 2 sockets on URL play?
Reply #1 –
BTW, I'm not saying that expecting the 2 GET requests on the same resource to return the same (or a streamable content, i.e. bound to a packet) is a wrong assessment, but it's a strong assessment that maybe does not need to be done. If the objective is to get the headers at first, with not making a HEAD request instead?
Here is a small example
12:29:23 192.168.2.10:11934 Connected
12:29:23 192.168.2.10:11934 Requested GET /BL16-44-flac.flac
12:29:23 192.168.2.10:11934 Request dump
> GET /BL16-44-flac.flac HTTP/1.1
> Host: 192.168.2.10:8080
> Connection: close
> User-Agent: foobar2000/1.4.3
> Accept: */*
> Icy-MetaData:1
12:29:23 192.168.2.10:11934 Sent 1460 bytes
12:29:23 192.168.2.10:11935 Connected
12:29:23 192.168.2.10:11935 Requested GET /BL16-44-flac.flac
12:29:23 192.168.2.10:11935 Request dump
> GET /BL16-44-flac.flac HTTP/1.1
> Host: 192.168.2.10:8080
> Connection: close
> User-Agent: foobar2000/1.4.3
> Accept: */*
> Icy-MetaData:1
12:29:23 192.168.2.10:11935 Sent 1460 bytes
12:29:23 192.168.2.10:11934 Disconnected - 48180 bytes sent
12:29:27 192.168.2.10:11935 Sent 598600 bytes
12:29:27 192.168.2.10:11935 Served 1021.0 K
12:29:27 192.168.2.10:11935 Fully downloaded - 1021.0 K @ 325.5 KB/s - /BL16-44-flac.flac
12:29:27 192.168.2.10:11935 Disconnected by server - 1045508 bytes sent