CSM, Reverse Proxy, and Sticky

[thethmon]

First, here is a diagram of my setup:

CSM w/VIP for Front-End Web Servers (acting as Authorization and Reverse Proxy)

|

SSL Module for termination of HTTPS traffic

|

Front-End Web Servers

|

CSM w/VIP for Back-end Web Servers

|

Back-end Web Servers

What I need a way to do is to ensure that users gets to the same Back-end Web Server for their entire session. The Front-End Web Servers act as a Reverse Proxy for all requests going to the Back-End Web Servers and are configured to send requests to the VIP for the Back-End Web Servers.

[Gilles Dufour]

Is this HTTP traffic from front-end to back-end or is this https ?

Assuming it is http, the best I would recommend is to use a cookie. If the backend-server let them generate a cookie and then just use sticky group cookie on the CSM vserver.

If the servers can't create cookies, you can configure the csm to do so with software version 4.1.

Regards,

Gilles.

[thethmon]

Gilles,

Thanks for the response. This is https traffic for the user, but from the Front-End to the Back-End it's just http. Unfortunately it's SAP so it's not a normal HTTP Back-end that can generate cookies. Currently I am only running 3.1(7). What is the status of the 4.1 train? Being new I am concerned about utilizing this level. What has been the experience of customers on this code level in the field?

[Gilles Dufour]

not much problem so far except a hang when using the offset/length option of the sticky cookie feature.

Gilles.