Hi, I noticed a strange behavior on the haproxy.org servers, which unfortunately is being triggered trying to download the source from a chef-client.
When downloading the tar.gz, the chef client sends ":80" as part of the host header (which is legal from my understanding of the rfc). This header reliably results in a 404, whereas leaving out the port number results in a successful download: This does not work: root@frontend2:~# curl -I -H "Host: haproxy.org:80" http://haproxy.org/download/1.5/src/haproxy-1.5.0.tar.gz HTTP/1.1 404 Not Found Date: Mon, 23 Jun 2014 12:03:01 GMT Server: Apache Content-Type: text/html; charset=iso-8859-1 This works: root@frontend2:~# curl -I -H "Host: haproxy.org" http://haproxy.org/download/1.5/src/haproxy-1.5.0.tar.gz HTTP/1.1 200 OK Date: Mon, 23 Jun 2014 12:03:05 GMT Server: Apache (Unix; Formilux/0.1.8) Last-Modified: Thu, 19 Jun 2014 19:06:22 GMT Accept-Ranges: bytes Content-Type: application/x-gzip Expires: Mon, 23 Jun 2014 13:58:48 GMT Cache-Control: max-age=28800 Content-Length: 1329040 Age: 21857 X-Cache: HIT from haproxy.org Set-Cookie: sid=c; path=/ Cache-control: private Do you consider this a misconfiguration as well and could this possibly be corrected? Altering the behavior of the chef client to leave out that superfluous port number is very cumbersome. cheers, bkw
