I manually turned off persistence with the "no persistence" cmd in the content rule. no dice.

is there a way to force a RST after each connection within the CSS?

When you configure no persistence on the content rule, you are instructing the CSS to initiate a non-persistence connection in the backend (to the server).

You can configure the global command "persistence reset remap", so the CSS will RST and remap each request, however this configuration is used when you have many content rules with same VIP and different layer 5 configuration, so you could have different server farms for different URLs, and then you would like to have the CSS checking at every request and remap if a more specific content rule is matched.

I do not think that this configuration would change your behavior with a single persistent connection from the browser to the same rule, but you might want to give it a try.

Hope it helps!!

there is no way.

If the css detects that there is no reason to change [no different url that would match a different rule or no new cookie ...] it will keep the connection with the current server.

This is to achieve better performance which is the ultimate goal of a loadbalancer.

If you have to close a connection and reopen it for each request your performance drops.

If this is still what you want, you should modify your servers - not the CSS.

Configure the servers to do HTTP 1.0 and not HTTP 1.1 and you will have a new connection for every request.

Gilles.

thanks for clarifying on this.

dayo