Both Greg and Joakim have provided answers to this on the mailing list
>From Greg: https://dev.eclipse.org/mhonarc/lists/jetty-users/msg07962.html
>From Joakim: https://dev.eclipse.org/mhonarc/lists/jetty-users/msg07976.html
Specifically, to quote Joakim:
The idea of a server side configuration for connection "keep-alive" really
> doesn't makes sense in any version of HTTP ... with a server that honors
> the HTTP spec properly.
> If the switch exists to enable "keep-alive", then it has no meaning in
> HTTP/1.1 and HTTP/2 (this is default behavior). To enable "keep-alive" in
> HTTP/1.0 requires the user-agent to send the "Connection: keep-alive"
> header (server cannot force this).
> If the switch exists to disable "keep-alive", then it has no need in
> HTTP/1.1 (just add the "Connection: close" header to your responses, in a
> filter or rewrite rule if you want). HTTP/2 cannot disable it, and HTTP/1.0
> is already behaving the way you want.
> So, in short, if you want persistent connections, use HTTP/1.1 (or
> HTTP/2), don't specify "Connection: close" (on client request headers or
> server response headers), and don't do anything that violates the HTTP spec
> (as that will be an error that closes the connection).
"Keep Alive" is not something Jetty-specific and there are no controls to
modify the behavior that are Jetty-specific. HTTP/2 Connections are
persistent by default <https://tools.ietf.org/html/rfc7540#section-9.1> as
are ones in HTTP 1.1 <https://tools.ietf.org/html/rfc7230#section-6.3>.
On Sun, Aug 6, 2017 at 3:06 PM, anurag gupta <anurag.11...@gmail.com> wrote:
> Are there any tweakable parameters for Keep-Alive in jetty ?
> jetty-users mailing list
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
jetty-users mailing list
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit