>
>I have a problem with the connection not closing
>after serving the answer of a cgi script.
That's an unavoidable problem with CGI scripts that do not - or cannot
-
provide a Content-Length and that are spawned by an HTTP/1.1 server.
There is no end-of-script marker, so the client can wait for CGI data
forever - or until the user clicks on a link and the client sends
a new request.
cgit and ls.cgi do not know the length of their payload in advance, so
they cannot provide a Content-Length.
There are several ways to work around it:
- Declare cgit and ls.cgi, as well as similar cgi scripts, as autochunk.
That is what I do, and it works well: chunked transfer-encoding has an
end-of-data marker. I think it's the optimal solution.
- If the output can be served as is to clients, mark cgit and ls.cgi
(and similar scripts) as NPH. When the script dies, the connection ends
and EOF is transmitted to the client. It is more expensive since you
cannot reuse the connection, but it works. It is basically what
HTTP/1.0 does.
>P.S.: "log debug" in /etc/tipidee.conf seems not to work.
It works, it's just that I haven't added many debug statements ^^"
Currently there is only one, and that's if you perform a local redirect.
--
Laurent
Received on Mon Jan 05 2026 - 22:18:07 CET