Hi all, Got no response to this first time round - need some feedback on this before I can commit it.
When proxy listens for a 100-continue response from a remote server, it
must only wait a short amount of time for a response - just in case it
connected to an HTTP/1.0 server that did not understand the Expect
header.
>From what I understood of timeouts, a soft timeout is what I was looking
for, but ap_soft_timeout() has a 300 second timeout read from the config
file. This new function adds a "short" timeout of 5 seconds, after which
proxy will give up waiting for 100-continue and send the request body
instead.
My question is thus "am I doing the right thing here"?
The actual 100-continue patch to the proxy will be posted separately.
Regards,
Graham
--
-----------------------------------------
[EMAIL PROTECTED] "There's a moon
over Bourbon Street
tonight..."
--- /home/minfrin/src/apache/pristine/apache-1.3/src/main/http_main.c Sun Mar 24
11:59:48 2002
+++ src/main/http_main.c Wed Apr 10 09:50:37 2002
@@ -1714,6 +1714,20 @@
ap_set_callback_and_alarm(timeout, r->server->timeout);
}
+/* a short timeout for handling possible 100-continue responses
+ * in proxy.
+ */
+#define SHORT_TIMEOUT 5
+
+API_EXPORT(void) ap_soft_short_timeout(char *name)
+{
+#ifdef NETWARE
+ get_tsd
+#endif
+ timeout_name = name;
+ ap_set_callback_and_alarm(timeout, SHORT_TIMEOUT);
+}
+
API_EXPORT(void) ap_kill_timeout(request_rec *dummy)
{
#ifdef NETWARE
smime.p7s
Description: S/MIME Cryptographic Signature
