Home/ Questions/Q 531177
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T09:16:24+00:00

"keep-alive" its there in HTTP. Some says it good should be used, but i

  • 0

"keep-alive" its there in HTTP. Some says it good should be used, but i am unable to get to any conclusion.
So please provide your input/answer/views so i can get some ground for this,

  1. What it does?

  2. Scenario where it should and should not be done?

  3. How it can make AJAX application better ?

  4. Risks DO’s and DONT’s if any?

    Thank you all for inputs.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    First off if your connection to the server is using HTTP/1.1 then you are most likely already using “keep-alive”.

    What is it? Logically HTTP is a connectionless protocol. That is each request/response to the server creates a new connection, does its business and drops the connection. However in HTTP/1.1 the default behaviour is to keep the connection open for use by subsequent requests to the server. The “keep-alive” header was added to HTTP/1.0 to allow this behaviour to be opted into, in HTTP/1.1 the server needs to opt-out by closing the connection itself and/or sending a “connection-close” header in response.

    Why is it beneficial? Creating a connection especially one that needs to be authenticated can take some time. By re-using an existing connection the setup and authentication effort is much reduced.

    How can it make your AJAX app better? You are probably already benefitting from it.

    What are the risks? When making a connection through a shared appliance which may make a connection to the server in the clients behalf it is possible for other clients to re-use the connection, however that also makes it possible for other clients to use a connection that the server has authenticated for a different user.

    • 0