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
Addendum:
This only happens on ipv4, ipv6 on 2001:7a8:363c:2::2 is fine:
bkw@Aeronaut:~$ curl -6 -I -H Host: haproxy.org:80
http://haproxy.org/download/1.5/src/haproxy-1.5.0.tar.gz
HTTP/1.1 200 OK
Date: Mon, 23 Jun 2014 12:38:00 GMT
Last-Modified: Thu, 19 Jun 2014 19:06:22 GMT
Accept-Ranges:
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
On 23.06.2014, at 16:50, Holger Just w...@meine-er.de wrote:
[2] https://gist.github.com/meineerde/83e044c709b94358a616
Perfect, that worked like charm, Thank you!
Still, I think it's really the servers who are to blame for misbehaving. I just
rechecked the following RFCs:
-
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
On Mon, Jun 23, 2014 at 07:32:53PM +0200, Bernhard Weißhuhn wrote:
On 23.06.2014, at 16:50, Holger Just w...@meine-er.de wrote:
[2] https://gist.github.com/meineerde/83e044c709b94358a616
Perfect, that worked like charm, Thank you!
Still, I think it's really the servers who are to blame
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 w...@1wt.eu 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
7 matches
Mail list logo
