DOC: config: Update doc for PR/PH session states to warn about rewrite failures

When an HTTP header rewrite failure is triggered, and 500-internal-error
response is returned. A "PR" termination state is logged if the error
occurred on the request and "PH" if the error is reported for the response.

The documentation was updated accordingly.

This patch is related to issue #1597.

diff --git a/doc/configuration.txt b/doc/configuration.txt
index 990b837709e21af66423361662f45ba5c893ab3e..0d6a1a5e6311e2489f277df3ce2d8fd0cab68ff1 100644 (file)
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -22375,12 +22375,18 @@ easier finding and understanding.
           rare, that the proxy blocked a chunked-encoding request from the
           client due to an invalid syntax, before the server responded. In this
           case, an HTTP 400 error is sent to the client and reported in the
-          logs.
+          logs. Finally, it may be due to an HTTP header rewrite failure on the
+          response. In this case, an HTTP 500 error is sent (see
+          "tune.maxrewrite" and "http-response strict-mode" for more
+          inforomation).
 
      PR   The proxy blocked the client's HTTP request, either because of an
           invalid HTTP syntax, in which case it returned an HTTP 400 error to
           the client, or because a deny filter matched, in which case it
-          returned an HTTP 403 error.
+          returned an HTTP 403 error.  It may also be due to an HTTP header
+          rewrite failure on the request. In this case, an HTTP 500 error is
+          sent (see "tune.maxrewrite" and "http-request strict-mode" for more
+          inforomation).
 
      PT   The proxy blocked the client's request and has tarpitted its
           connection before returning it a 500 server error. Nothing was sent