Hi,
We've been using haproxy in docker for quite some time to provide reverse
proxy facilities for many and varied application servers. Typically, we've
always used option http-server-close in the config, except for rare
occasions where we might need http-keep-alive (eg ntlm authentication). We
also have the following in our front end configs:
compression algo gzip
compression type text/html application/x-javascript text/css
application/javascript text/javascript text/plain text/xml application/json
application/vnd.ms-fontobject application/x-font-opentype
application/x-font-truetype application/x-font-ttf application/xml font/eot
font/opentype font/otf image/svg+xml image/vnd.microsoft.icon
These have been working fine up to and including the most recent release of
1.7. We've recently began re-engineering our reverse proxy set up, and as
part of this we want to move to 1.8. However, we've discovered that some
resources requested by web pages (mainly javascript and css) don't load
properly when using haproxy 1.8 with these options. Basically, the page
doesn't display and the developer toolbar in Chrome gives an error of
net::ERR_INCOMPLETE_CHUNKED_ENCODING or net::ERR_INVALID_CHUNKED_ENCODING
against the resources that failed to load in the network pane. I haven't
been able to determine yet why this doesn't apply to every resource the
page attempts to load, but in this case out of 20 javascript and css files,
5 fail to load.
We've noticed that the problem goes away when using option http-keep-alive
and option http-pretend-keepalive, but as the documentation suggests that
http-server-close is the preferred option, we'd prefer to stick with that.
Can anyone offer any advice?
Thanks
--
Martin Goldstone
IT Systems Administrator
IT Services, Innovation Centre 1 (IC1)
Keele University, Keele, Staffordshire, United Kingdom, ST5 5NB
Telephone: +44 1782 734457
G+: http://google.com/+MartinGoldstoneKeele
