Message -
From: Adam Sussman [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, January 01, 2002 9:35 PM
Subject: Re: [PATCH] mod_proxy infinite cpu eating loop
Bill,
Everything looks good except that ap_proxy_string_read() now segfaults on
its apr_bucket_read(). It appears
Can you identify where the seg fault is happening? I am really suspicious of why
checking
for length == 0 would avoid the segfault. As I mentioned in an earlier post, I suspect
this check is masking another problem.
Thanks,
Bill
Bill,
Everything looks good except that
On Wed, Jan 02, 2002 at 01:34:57PM -0500, Bill Stoddard wrote:
I see this pattern several places in the code:
rc = apr_get_brigade();
if (rc != APR_SUCCESS) {
fail;
}
/* Is the brigade empty? */
if (APR_BRIGADE_EMPTY(b)) {
fail;
}
/* Get first bucket */
e =
On Wednesday 02 January 2002 10:34 am, Bill Stoddard wrote:
I see this pattern several places in the code:
rc = apr_get_brigade();
if (rc != APR_SUCCESS) {
fail;
}
/* Is the brigade empty? */
if (APR_BRIGADE_EMPTY(b)) {
fail;
}
/* Get first bucket */
e = APR_BRIGADE_FIRST(b);
On Wednesday 02 January 2002 10:34 am, Bill Stoddard wrote:
I see this pattern several places in the code:
rc = apr_get_brigade();
if (rc != APR_SUCCESS) {
fail;
}
/* Is the brigade empty? */
if (APR_BRIGADE_EMPTY(b)) {
fail;
}
/* Get first bucket */
e =
see an HTTP/1.10
*/
- Original Message -
From: Adam Sussman [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, December 28, 2001 8:24 PM
Subject: [PATCH] mod_proxy infinite cpu eating loop
ap_proxy_string_read currently goes into an infinite loop when
= strlen(buffer);
-
+#endif
/* Is it an HTTP/1 response?
* This is buggy if we ever see an HTTP/1.10
*/
- Original Message -
From: Adam Sussman [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, December 28, 2001 8:24 PM
Subject: [PATCH] mod_proxy infinite cpu
PROTECTED]
Sent: Friday, December 28, 2001 8:24 PM
Subject: [PATCH] mod_proxy infinite cpu eating loop
ap_proxy_string_read currently goes into an infinite loop when the proxied server
closes the connection without sending any data. This patch fixes the problem
but I am not sure
