[MEDIUM] http: properly handle "option forceclose"
The "forceclose" option used to close the output channel to the
server once it started to respond. While this happened to work with
most servers, some of them considered this as a connection abort and
immediately stopped responding.
Now that we're aware of the end of a request and response, we're able
to trivially handle this option and properly close both sides when the
server's response is complete.
During this change it appeared that forwarding could be allowed when
the BF_SHUTW_NOW flag was set on a buffer, which obviously is not
acceptable and was causing some trouble. This has been fixed too and
is the reason for the MEDIUM status on this patch.
diff --git a/doc/configuration.txt b/doc/configuration.txt
index 4cafff8..e69aa7c 100644
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -2393,10 +2393,8 @@
global session times in the logs.
When this happens, it is possible to use "option forceclose". It will
- actively close the outgoing server channel as soon as the server begins to
- reply and only if the request buffer is empty. Note that this should NOT be
- used if CONNECT requests are expected between the client and the server. This
- option implicitly enables the "httpclose" option.
+ actively close the outgoing server channel as soon as the server has finished
+ to respond. This option implicitly enables the "httpclose" option.
If this option has been enabled in a "defaults" section, it can be disabled
in a specific instance by prepending the "no" keyword before it.