20014internal Error Proxy Error Reading Status Line From Remote Server
Contents |
Forgot Password Login: [x] First Last Prev Next This bug is not in your last search results. Bug48037 - mod_proxy_http does not handle asynchronous keepalive close events correctly Summary:
Internal Error Proxy Error Reading Status Line From Remote Server Localhost
mod_proxy_http does not handle asynchronous keepalive close events correctly Status: NEW Product: Apache httpd-2 proxy error reading status line from remote server apache Classification: Unclassified Component: mod_proxy_http Version: 2.0.63 Hardware: PC Linux Importance: P2 normal with 2 votes (vote) TargetMilestone: --- Assigned To: Apache connection reset by peer proxy error reading status line from remote server HTTPD Bugs Mailing List URL: Keywords: Depends on: Blocks: Show dependency tree Reported: 2009-10-21 16:35 UTC by John Lightsey Modified: 2016-08-01 03:04 UTC (History) CC List: 4 users (show) helen jd sokann
The Timeout Specified Has Expired Proxy Error Reading Status Line From Remote Server
williama_lovaton Attachments server config files (3.82 KB, application/zip) 2016-01-11 11:30 UTC, Helen Details Server Config files (3.82 KB, application/zip) 2016-01-11 11:32 UTC, Helen Details View All Add an attachment (proposed patch, testcase, etc.) Note You need to log in before you can comment on or make changes to this bug. Description John Lightsey 2009-10-21 16:35:38 UTC Noticed this with Apache 2.0.63, but it looks fairly clear that the
104 Connection Reset By Peer Proxy Error Reading Status Line From Remote Server
same problem exists in 2.2.14. The way proxy_httpd.c is written, if a keepalive connection is closed by the other side in ap_proxy_http_handler() after ap_proxy_http_create_connection() and before a response is received, Apache will consider this to be a connection error and generate a 502 response. This logic is only valid on the first request across the keepalive. According to the HTTP 1.1 spec, proxy_httpd.c must be capable of handling asynchronous close events in the middle of a keepalive session. When it encounters an unexpected close it should attempt to reestablish the connection and resend the request before generating a 502 response. Comment 1 Ruediger Pluem 2012-08-10 06:39:44 UTC Please check a recent 2.2.x / 2.4.x. This should have the problem fixed. Comment 2 William Lovaton 2013-04-13 18:16:43 UTC Sorry, but this problem is still happening. I'm testing httpd 2.2.23 from http://centos.alt.ru/repository/centos/6/x86_64/ repository on a RHEL 6.4 server. I was seeing the same problem from official RHEL packages (httpd-2.2.15-26.el6.x86_64.rpm) and updating to 2.2.23 didn't solve the problem. My configuration is as follows: * Reverse Proxy: RHEL 6.4 with apache 2.2.23 from CentosALT (Worker MPM) * Backend Servers: 2 x RHEL 6.2 with apache 2.2.15-15.el6.x86_64 from RHEL (Prefork MPM, huge in-house PHP 5 web app) I'm usin
[x] First Last Prev Next This bug is not in your last search results. 70007 the timeout specified has expired proxy error reading status line from remote server Bug37770 - proxy: error reading status line from remote server (null)
Proxy-initial-not-pooled
Summary: proxy: error reading status line from remote server (null) Status: REOPENED Product: Apache httpd-2 Classification: ah00898: error reading from remote server returned by Unclassified Component: mod_proxy Version: 2.2.3 Hardware: Sun Solaris Importance: P1 blocker with 29 votes (vote) TargetMilestone: --- Assigned To: Apache HTTPD Bugs Mailing List URL: http://extra.gatema.cz/Test42/Data.asmx Keywords: ErrorMessage https://bz.apache.org/bugzilla/show_bug.cgi?id=48037 Duplicates: 32731 37876 39499 39629 41150 44079 45588 46504 57520 (view as bug list) Depends on: Blocks: Show dependency tree Reported: 2005-12-03 13:40 UTC by Christophe Yayon Modified: 2015-10-27 07:35 UTC (History) CC List: 26 users (show) alejandro.cavallo anup.mittal apache bill+apache brett chris denis.kranjcec dkruglyak japs jconley jibanes jmehta jtharp kirant400 marado milan.pospisil mirkwood09+spamkill https://bz.apache.org/bugzilla/show_bug.cgi?id=37770 paul.kmiec ronn.chinowutthichai rvandolson suresh.pagadala tapan.nanawati thierry.trinh todorz vladap yneko Attachments backend connection race condition fix (untested) (2.88 KB, patch) 2007-12-07 07:31 UTC, Aleksey Midenkov Details | Diff Patch against trunk (1.71 KB, patch) 2008-07-31 13:23 UTC, Ruediger Pluem Details | Diff View All Add an attachment (proposed patch, testcase, etc.) Note You need to log in before you can comment on or make changes to this bug. Description Christophe Yayon 2005-12-03 13:40:17 UTC Hi all, I have configured httpd-2.2.0 (release) with mod_proxy and virtual hosting and when i stress it, even low (10 simultaneous users with Mercury Load Runner) i get some errors messages and status code 502 on the client browser. The problem occurs only when i do some load tests, when i request from single client i have no problem... My error.log : [Sat Dec 03 13:16:25 2005] [error] [client 10.133.2.63] proxy: error reading status line from remote server (null), referer: http://portail.polen.xxxxx.fr/ [Sat Dec 03 13:16:25 2005] [error] [client 10.133.2.63] proxy: Error
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About http://stackoverflow.com/questions/9834318/the-proxy-server-received-an-invalid-response-from-an-upstream-server Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up The proxy server received an invalid response error reading from an upstream server [closed] up vote 22 down vote favorite 6 We have an application deployed on tomcat. To access application we are using apache which sends requests to tomcat. At random browser gives following response. Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /sampleapp/