@kode54 : Yes indeed, you're right about the error message source. But I'm using my proxy for everything both HTTP and HTTPS, without any issue so far.
Explanation
My whole network is designed to force everything that goes out to be secured as well as what enters it. So I'm using outgoing proxy [Squid 3.4.8] to validate and authorize urls, filter advertisment, porn, etc. This has sometimes a drawback as most software designers consider that their wonderful software must have unrestricted access to the Internet and I found various situation where I had to choose either to open holes in my security or stop running a piece of software.
In this case, the proxy is well requested by foobar2000 and the requests are going through it. However it seems that the request is either malformed or missing something and it is blocked by the proxy.
From Squid access.log, here's what I get with a standard working request:
HTTP/1.1 200 TCP_TUNNEL CONNECT -
Here's what I get with a foobar2000 request:
HTTP/1.1 501 TAG_NONE - text/html
When I use Wireshark to go deeper, I get this when in proxy mode:
GET https://www.foobar2000.org/update-core?version=1%2E4+beta+11&beta&challenge=6B5B4FC1%2D5133%2D42B6%2DB22E%2DC2A4DA6E37AA HTTP/1.1
Connection: close
User-Agent: foobar2000/1.x
Accept: */*
And the packet window gives me this :
151 6.121482 10.100.200.253 10.100.200.251 HTTP 251 GET https://www.foobar2000.org/update-core?version=1%2E4+beta+11&beta&challenge=6B5B4FC1%2D5133%2D42B6%2DB22E%2DC2A4DA6E37AA HTTP/1.1
Well, I don't have time now to go further. On my side, I have a workaround : bypass the proxy for foobar2000 update requests. However, as I am having other working HTTPS through the proxy, I think the problem is still here and should give some fun to the programmers team. If you think I'm doing it wrong, please let me know.