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 heade
ept-Ranges: bytes
Content-Length: 1329040
Cache-Control: max-age=28800
Expires: Mon, 23 Jun 2014 20:38:00 GMT
Content-Type: application/x-gzip
Server: Apache (Unix; Formilux/0.1.8)
On 23.06.2014, at 14:08, Bernhard Weißhuhn wrote:
> Hi,
>
> I noticed a strange behavior on the haproxy
On 23.06.2014, at 16:50, Holger Just 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:
- http://tools.ietf.org/html/rfc72
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 wrote:
> Hi,
>
> On Mon, Jun 23, 2014 at 02:08:57PM +0200, Bernhard Weißhuhn wrote:
>> Hi,
>>
>> I noticed a strange
4 matches
Mail list logo
