CSS 7.20 B 203 - HTTP Keepalives 1.0 and 1.1

Sbutzek — Wed, 01 Sep 2004 16:21:08 GMT

Hi,

we just upgradet from 7.20 Build 109 to 7.30 B 203.

So we see some changes in Keepalive behaviour.

Having many Services with keepalive type http and get.

The keepalive with method head works.

In the new Version the Requests on some Keepalives are sent as http 1.1. If this happens, then our keepalive comes first alive and is then getting down.

Not sure, why. The Error messeage is "General Read failure".

If we Change to http non-persistent then the keepalive comes with HTTP 1.0 and anything is fine.

But the strange thing is, some keepalives are not configured to non-persistent and they also come with http 1.0. The are also working.

How the CSS decides to send HTTP 1.0 or 1.1 Request.

Was there a Change on Keepalives? I have not found anything on the releasenotes.

Best Regards

Sven

Re: CSS 7.20 B 203 - HTTP Keepalives 1.0 and 1.1

Gilles Dufour — Thu, 02 Sep 2004 07:55:48 GMT

there is a well-known bug that matches your description

CSCed85319 The CSS is configured with persistent HTTP keepalives. If the server response to the HTTP 1.1 keepalive request contained "Connection: Keep-Alive", the CSS would incorrectly downgrade the HTTP 1.1 keepalive (persistent) to a HTTP 1.0 keepalive (non-persistent).

What is strange is that your old version was affected and the new one should fix it.

In your current version there is also this know issue :

CSCef39490 keepalive method GET has issue with hex 20

Could you capture a trace and post it to this forum.

Thanks,

Gilles.

topic CSS 7.20 B 203 - HTTP Keepalives 1.0 and 1.1 in Application Networking

CSS 7.20 B 203 - HTTP Keepalives 1.0 and 1.1

Re: CSS 7.20 B 203 - HTTP Keepalives 1.0 and 1.1