20014internal Error Proxy Error
Contents |
Forgot Password Login: [x] First Last Prev Next This bug is not in your last search results. Bug48037 - proxy: error reading status line from remote server mod_proxy_http does not handle asynchronous keepalive close events correctly Summary: mod_proxy_http apache 20014 internal error does not handle asynchronous keepalive close events correctly Status: NEW Product: Apache httpd-2 Classification: Unclassified Component: mod_proxy_http Version: proxy-initial-not-pooled 2.0.63 Hardware: PC Linux Importance: P2 normal with 2 votes (vote) TargetMilestone: --- Assigned To: Apache HTTPD Bugs Mailing List URL: Keywords: Depends on: Blocks: Show dependency ah00898: error reading from remote server returned by 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 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
Error Reading Status Line From Remote Server Localhost
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 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/repos
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 Us Learn more
(70007)the Timeout Specified Has Expired: Proxy: Error Reading Status Line From Remote Server
about Stack Overflow the company Business Learn more about hiring developers or posting connection reset by peer proxy error reading status line from remote server ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack setenv proxy-initial-not-pooled Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Mod_Proxy 502-Proxy Error intermittently up vote 6 down vote favorite I'm https://bz.apache.org/bugzilla/show_bug.cgi?id=48037 Using Apache 2.2.16 and Tomcat 7.0.16. I have 3 Tomcat instance which executes 3 different war files. To bypass the request I have configured httpd with mod_proxy. 3 Tomcat instances are running in 8080, 8090, 8099. find the httpd configuration below ProxyPass /bor `http://localhost:8080/bor/ ProxyPass /borcafews/ `http://localhost:8090/borcafews/ ProxyPass /borechws/ `http://localhost:8099/borechws/ Intermittently I was getting 502 Proxy Error in 8090 and 8099. So I have set the below variables in http://stackoverflow.com/questions/12006860/mod-proxy-502-proxy-error-intermittently the httpd.conf
proxy functionality to pass traffic back and forth. What we error reading started seeing under load was the following: (20014)Internal error: proxy: error reading status line from remote server 127.0.0.1 To fix this I from remote server added these two lines in our locationmatch containers: SetEnv force-proxy-request-1.0 1 SetEnv proxy-nokeepalive 1 This appears to have resolved our issue. Tagged on: Apache Error, Apache How-To By RElliott Technologies | May 22, 2013 | Apache, Glassfish | ← Zend 6 - Installation Apache - 417 error → Copyright © 2016 RElliott Technologies | Theme by: Theme Horse | Powered by: WordPress Back to Top