Hi Bernhard, Bernhard Weißhuhn wrote: >> 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 happens because chef creates an unusual Host-header for its remote_file resources right now. This currently doesn't only break for haproxy.org but for many other services. The issue is fixed in the chef master branch already [1]. To use the fix right now, you can add a monkey-patch into one of your cookbooks which patches chef's core with the fix [2]. The linked gist is a direct translation of the patch. I use this currently in production if that matters to you. Regards, Holger [1] https://github.com/opscode/chef/pull/1471 [2] https://gist.github.com/meineerde/83e044c709b94358a616
