Slow response with SSL (https) on CSS

rv_viji · ‎01-04-2008

Hi,

Our network topology is as per the attachement â€œCSS Topology Diag.jpgâ€. The users behind the CORE network will access the application through the VIP address â€œ192.168.10.171â€. SSL card has been installed on the CSS's and the SSL gets terminated on the CSS. The traffic between CSS and the physical servers are on â€œhttpâ€.

Now when the users tries to access the application using SSL (https://192.168.10.171) the application response is very slow, however when the users tries to access the application using http (http://192.168.10.171) application response is ok.

Find the attached configurations of the primary and secondary CSS. Any inputs to resolve this issue..??

(Note: It take nearly 20 - 30 seconds to get the page when users initiate a connection through https and however when the users initiate the http connection page gets displayed in 2 - 3 seconds)

Regards

Gilles Dufour · ‎01-05-2008

Try the following commands

ssl-server X ssl-queue-delay 0

ssl-server X tcp server ack-delay 0

ssl-server X tcp virtual ack-delay 0

If the problem persists, get a sniffer trace on client side and server side simultaneous.

Gilles.

rv_viji · ‎01-05-2008

Hi Gilles,

Still problem persists, find the attached sinffer logs captured on both Client Side and CSS side..

Regards

rv_viji · ‎01-05-2008

Hi Gilles,

Also attached the sniffer logs for http traffic...

Regards

Gilles Dufour · ‎01-05-2008

the traffic having issue is HTTPS not HTTP.

So we want to see a trace with HTTPS.

Also, get the trace on the client and on the server - not the CSS. (we want to see both side of the css)

Gilles.

rv_viji · ‎01-05-2008

Hi Gilles,

I have attached the https logs in my previous reply to this post.

And regarding the server side trace, I will post it soon... however just to mention the ssl traffic (https)gets terminated on the CSS and from the CSS to the servers it is http traffic....

Regards

Gilles Dufour · ‎01-06-2008

there is absolutely no SSL/HTTPS traffic in the 2 traces you sent. Only HTTP.

I would expect your client trace to contain SSL traffic.

G.

prakashj · ‎01-25-2008

we ar facing the same issues,

please post immedietily

jslepicka · ‎01-25-2008

try:

ssl-server 1 ssl-queue-delay 0