On Wed, Sep 28, 2016 at 2:51 AM Lukas Tribus <[email protected]> wrote: > Hi David, > > > Am 28.09.2016 um 00:40 schrieb David Birdsong: > > I managed to disable keepalive properly and now I see the problem > > completely resolve itself. > > > > Is there some way to use mixed-content frontends w/ a previously > > opened connection and still detect HTTP (the default HTTP acl)? > > Provide the complete configuration and the exact release you are using > as this behavior heavily depends on the defaults that changed over time > and the actual keep-alive mode configured. >
complete config: https://gist.github.com/davidbirdsong/b0970da66b4f5a716c33a2bef087b467 the version is: HA-Proxy version 1.6.7 2016/07/13 > > > I assume you use haproxy 1.4 which defaulted to tunnel-mode. You can > configure "option http-server-close" to use keep-alive on the frontend > and no keepalive on the backend or upgrade to 1.6 and configure proper > keep-alive. > I had " "option http-server-close" and wondered if this was the source of the problem since http-type connections would be disconnected server-side and therefore need content inspection on subsequent http requests that arrived on a previously used tcp connection. I tried disabling it, but found that any keepalive requests would get routed to the tcp-mode backend: "cdn-parsers" still. For now, I've disabled keepalive by adding: "option httpclose" to the http backend which resolves the issue, but I'd love to restore keepalive. > > > BR, > Lukas > >
