|
to Eric first thanks a lot. > Do they really come together for the same request? these 2 errors are not the same request.but they often appear together. >The first seems > like you tried to proxy a request and the remote side closed the > keepalive connection -- you can disable keepalive in the HTTP proxy. i have tried it. i have set httpd.conf file's [KeepAlive = Off].but proxy can work normally.web page also appear normally. i also found the source where happen this error. but i don't know the source's how to handle it and when can cause the error. source: httpd-2.0.47\modules\proxy\proxy_http.c 639: status = ap_pass_brigade(origin->output_filters, bb); 640: 641: if (status != APR_SUCCESS) { 642: ap_log_error(APLOG_MARK, APLOG_ERR, status, r-> server, 643: "proxy: request failed to %pI (%s)", 644: p_conn->addr, p_conn->name); 645: return status; 646: } if you know the souce's handle. what condition can cause status=104 or status =70007 ,please tell me. Grant chen. > Date: Sun, 18 Jan 2009 22:00:20 -0500 > From: covener@xxxxxxxxx > To: kucss@xxxxxxxxxxx > Subject: Re: The timeout specified has expired in Apache2.0.47 > > On Sun, Jan 18, 2009 at 9:45 PM, chenGrant <kucss@xxxxxxxxxxx> wrote: > > to Eric > > hi ,this is grant. > >> I don't know why you can't simulate the error. You're much better off > >> with An Apache 2.2.x -based proxy server. > > > > my apace version also Apache2.0.47. i have got the below detail 2 error > > message. > > error_log: > > (104)Connection reset by peer:proxy:request failed to IP > > (70007)the timeout specified has expired:proxy:request failed to IP > > Do they really come together for the same request? The first seems > like you tried to proxy a request and the remote side closed the > keepalive connection -- you can disable keepalive in the HTTP proxy. > > -- > Eric Covener > covener@xxxxxxxxx 更多热辣资讯尽在新版MSN首页！ 立刻访问！ |
|