Hi David,
> 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?
Why not simply configure a sane keep-alive timeout with "timeout
http-keep-alive"? You are currently keeping the tcp connections up
for more than 8 minutes (500 seconds), are you aware of that?
1 or 2 seconds should be enough, this way you will probably not
run into this issue, correct?
Anyway, the idea with a redirect URL seems to be valid, does
your /redirect configuration work (I don't see why it wouldn't)?
Regards,
Lukas
