Confirmed, it works now. Two fixes for one problem within hours - you guys are amazing!
cheers, bkw On 23.06.2014, at 19:56, Willy Tarreau <[email protected]> wrote: > Hi, > > On Mon, Jun 23, 2014 at 02:08:57PM +0200, Bernhard Weißhuhn wrote: >> 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: > > OK I found why. The front server's haproxy used to send those ":80" to the > local cached copy of the site because they didn't match a configured pattern. > I've fixed that now. I'll now have to check why the local cache returns a > 404 :-) > > Thanks for reporting this! > Willy >
