From ff9c276c144bc24c70f1d5b531a8fd412c34c3d9 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Fri, 13 Oct 2023 12:17:45 +0000 Subject: Improved logging system Signed-off-by: Laurent Bercot --- doc/tipideed.html | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) (limited to 'doc/tipideed.html') diff --git a/doc/tipideed.html b/doc/tipideed.html index 977317c..1d764ff 100644 --- a/doc/tipideed.html +++ b/doc/tipideed.html @@ -91,15 +91,14 @@ of the tipidee package provides service templates to help you run tipideed under
0
Clean exit. There was a successful stream of HTTP exchanges, -that the client decided to end — including by being inactive long enough -that tipideed closes the connection on its own initiative, which is permitted -by HTTP.
+that either tipideed or the client decided to end in a way that is +permitted by HTTP.
1
Illicit client behaviour. tipideed exited because it could not serve the client in good faith.
2
Illicit CGI script behaviour. tipideed exited because the invoked CGI script made it impossible to continue. Before exiting, tipideed likely has sent a 502 (Bad Gateway) response to the client.
-
100
Bad usage. tipideed has been run in an incorrect way: bad command +
100
Bad usage. tipideed was run in an incorrect way: bad command line options, or missing environment variables, etc.
101
Cannot happen. This signals a bug in tipideed, and comes with an error message asking you to report the bug. Please do so, on the @@ -108,9 +107,8 @@ error message asking you to report the bug. Please do so, on the data or in the document layout that it does not like. This can happen, for instance, when a document is a symbolic link pointing outside of the server's root.
-
111
System call failed. If this happens while serving a request, -tipideed likely has sent a 500 (Internal Server Error) response to the -client before exiting.
+
111
System call failed. This usually signals a problem with the +underlying system.
-- cgit v1.3.1