Project

General

Profile

Actions
Copy link

Feature #1284

closed

lighttpd don't print keep alive answering header

Added by joungkyun over 17 years ago. Updated about 16 years ago.

Status:
Wontfix
Priority:
Normal
Category:
core
Target version:
1.4.20
ASK QUESTIONS IN Forums:

Description

lighttpd only print answering header "Connection: close" about Keep Alive. But Any programs check answering header as follows:


Connection: Keep-Alive
Keep-Alive: timeout=60, max=1000

This patch print upper answering headers for Keep Alive status, and has same operation with Apache web server.

Files

lighttpd-keepalive-header.patch (2.38 KB) lighttpd-keepalive-header.patch joungkyun, 2007-08-03 09:29
Actions
Copy link
 #1

Updated by jan over 17 years ago

  • Status changed from New to Assigned

For HTTP/1.1


Connection: Keep-Alive

is the default and doesn't have to be specified.

The Keep-Alive header is not specified in the RFC 2616 and I wonder where it is documented.

Actions
Copy link
 #2

Updated by joungkyun over 17 years ago

Keep-Alive: header is optional. (http://tools.ietf.org/html/rfc2068 19.7.1.1)

But, sometimes some libraries (for example, libtorrent and so on..) check this header. So, I want to be support this function on lighttpd.

Actions
Copy link
 #3

Updated by stbuehler over 16 years ago

  • Status changed from Assigned to Fixed
  • Resolution set to wontfix

The Keep-Alive header itself is optional, and is used only if a
parameter is being sent. HTTP/1.1 does not define any parameters.

So there are no standard params, there is reason to use it.

Actions
Copy link
 #4

Updated by stbuehler about 16 years ago

  • Status changed from Fixed to Wontfix
Actions
Copy link

Also available in: Atom