Baptiste,

Thanks for your help. I'm using HAProxy 1.5.4 and here's my config:

global
    log /dev/log    local0
    log /dev/log    local1 notice
    chroot /var/lib/haproxy
    stats socket /run/haproxy/admin.sock mode 660 level admin
    stats timeout 30s
    user haproxy
    group haproxy
    daemon

defaults
    log    global
    mode    http
        option forwardfor
    option http-server-close
        # option forceclose
    option    httplog
    option    dontlognull
        timeout connect 500000
        timeout client  5000000
        timeout server  5000000
    errorfile 400 /etc/haproxy/errors/400.http
    errorfile 403 /etc/haproxy/errors/403.http
    errorfile 408 /etc/haproxy/errors/408.http
    errorfile 500 /etc/haproxy/errors/500.http
    errorfile 502 /etc/haproxy/errors/502.http
    errorfile 503 /etc/haproxy/errors/503.http
    errorfile 504 /etc/haproxy/errors/504.http


frontend www-http
   bind *:80
   use_backend Jetty-close if { path_beg /redirect }
   default_backend Jetty


backend Jetty
        server jetty localhost:8080

backend Jetty-close
    option forceclose
        server jetty localhost:8080



On Wed, Oct 1, 2014 at 8:12 AM, Baptiste <[email protected]> wrote:

> On Wed, Oct 1, 2014 at 2:07 PM, David Pollak
> <[email protected]> wrote:
> > Howdy,
> >
> > I'm using HAProxy to choose among a series of dynamically allocated HTTP
> > backends. Basically, a user goes to URL A and clicks on the "start my
> > service" link. A new browser window/tab is popped up and they get the new
> > service/URL in the tab.
> >
> > Basically, got to /service click on a link, get a new browser window at
> > /special/xxxxx where the xxxx piece is routed to the dynamically created
> > service for that user.
> >
> > On the back end, the service is created in my cluster and I update
> > haproxy.cfg and do a "service haproxy reload".
> >
> > The issue I seem to be facing is that the browser has a keep-alive'd
> > connection to my server so the http request goes to the old HAProxy
> > instance.
> >
> > Is there a way to selectively force close the keep-alive for just the
> > browser that connects to the /special/xxxxx URL? Or maybe insert an
> > intermediate redirect URL that forces the close so the browser is forced
> to
> > re-establish a connection to the new HAProxy instance?
> >
> > Thanks,
> >
> > David
> >
>
> Hi David,
>
> I'm the person behind @haproxy_tech twitter account :)
>
> Could you please post your "anonymized) configuration and tell us
> which version of HAProxy you're using.
> With these information, I'll be able to understand what happens
> exactly and give you an accurate response.
>
> Baptiste
>



-- 
Brick Alloy http://brickalloy.com <https://telegr.am>
Lift, the simply functional web framework http://liftweb.net
Follow me: http://twitter.com/dpp
Blog: http://goodstuff.im

Reply via email to