Proxy Error Reading Status Line From Remote
Contents |
href="../mod/mod_proxy.html">mod_proxy Status:Extension Module Identifier:proxy_http_module Source File:mod_proxy_http.c Summary This module requires the service of mod_proxy. It provides the features used for proxying HTTP and HTTPS requests. (20014)internal error: proxy: error reading status line from remote server mod_proxy_http supports HTTP/0.9, HTTP/1.0 and HTTP/1.1. It does not provide any caching
Ah00898: Error Reading From Remote Server Returned By
abilities. If you want to set up a caching proxy, you might want to use the additional service (104)connection reset by peer: proxy: error reading status line from remote server of the mod_cache module. Thus, in order to get the ability of handling HTTP proxy requests, mod_proxy and mod_proxy_http have to be present in the server. Warning Do
Proxy-initial-not-pooled
not enable proxying until you have secured your server. Open proxy servers are dangerous both to your network and to the Internet at large. Topics Environment Variables Request notes Directives This module provides no directives. Bugfix checklisthttpd changelogKnown issuesReport a bugSee also mod_proxy mod_proxy_connect Comments Environment Variables In addition to the configuration directives that control the behaviour of mod_proxy, there are a number of environment variables that control the HTTP protocol provider. Environment variables below that don't specify specific values are enabled when set to any value. proxy-sendextracrlf Causes proxy to send an extra CR-LF newline on the end of a request. This is a workaround for a bug in some browsers. force-proxy-request-1.0 Forces the proxy to send requests to the backend as HTTP/1.0 and disables HTTP/1.1 features. proxy-nokeepalive Forces the proxy to close the backend connection after each request. proxy-chain-auth If the proxy requires authentication, it will read and consume the proxy authentication credentials sent by the client. With proxy-chain-auth it will also forward the credentials to the next proxy in the chain. This may be necessary if you have a chain of proxies that share authentication information. Security Warning: Do not set this unless you know you need it, as it forwards sensitive information! proxy-sendcl HTTP/1.0 required all HTTP requests that include a body (e.g. POST requests) to include a Content-Length header. This environment variable forces the Apache proxy to send this header to the backend server, regardless of
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and
Error Reading Status Line From Remote Server Localhost
policies of this site About Us Learn more about Stack Overflow the
Setenv Proxy-nokeepalive 1
company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered (70007)the timeout specified has expired: proxy: error reading status line from remote server Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can https://httpd.apache.org/docs/current/mod/mod_proxy_http.html ask a question Anybody can answer The best answers are voted up and rise to the top Proxy Error 502 “Reason: Error reading from remote server” with Apache 2.2.3 (Debian) mod_proxy and Jetty 6.1.18 up vote 47 down vote favorite 24 Apache is receiving requests at port :80 and proxying them to Jetty at port :8080 The proxy server received an invalid http://serverfault.com/questions/185894/proxy-error-502-reason-error-reading-from-remote-server-with-apache-2-2-3-de response from an upstream server The proxy server could not handle the request GET /. My dilemma: Everything works fine normally (fast requests, few seconds or few tens of seconds long requests are processed ok). Problems occur when request processing takes long (few minutes?). If I issue request instead directly to Jetty at port :8080 the request is processed OK. So problem is likely to sit somewhere between Apache and Jetty where I am using mod_proxy. How to solve this? I have already tried some "tricks" related to KeepAlive settings, without luck. Here is my current configuration, any suggestions? #keepalive Off ## I have tried this, does not help #SetEnv force-proxy-request-1.0 1 ## I have tried this, does not help #SetEnv proxy-nokeepalive 1 ## I have tried this, does not help #SetEnv proxy-initial-not-pooled 1 ## I have tried this, does not help KeepAlive 20 ## I have tried this, does not help KeepAliveTimeout 600 ## I have tried this, does not help ProxyTimeout 600 ## I have tried this, does not help NameVirtualHost *:80
Red Hat Certificate System Red Hat Satellite Subscription Asset Manager Red Hat Update Infrastructure Red Hat Insights Ansible Tower by Red https://access.redhat.com/solutions/54579 Hat Cloud Computing Back Red Hat CloudForms Red Hat OpenStack Platform http://apache-http-server.18135.x6.nabble.com/mod-proxy-error-reading-status-line-td5003910.html Red Hat Cloud Infrastructure Red Hat Cloud Suite Red Hat OpenShift Container Platform Red Hat OpenShift Online Red Hat OpenShift Dedicated Storage Back Red Hat Gluster Storage Red Hat Ceph Storage JBoss Development and Management Back Red Hat JBoss Enterprise Application Platform Red Hat JBoss error reading Data Grid Red Hat JBoss Web Server Red Hat JBoss Portal Red Hat JBoss Operations Network Red Hat JBoss Developer Studio JBoss Integration and Automation Back Red Hat JBoss Data Virtualization Red Hat JBoss Fuse Red Hat JBoss A-MQ Red Hat JBoss BPM Suite Red Hat JBoss BRMS Mobile Back Red Hat Mobile Application Platform Services error reading status Back Consulting Technical Account Management Training & Certifications Red Hat Enterprise Linux Developer Program Support Get Support Production Support Development Support Product Life Cycle & Update Policies Knowledge Search Documentation Knowledgebase Videos Discussions Ecosystem Browse Certified Solutions Overview Partner Resources Tools Back Red Hat Insights Learn More Red Hat Access Labs Explore Labs Configuration Deployment Troubleshooting Security Additional Tools Red Hat Access plug-ins Red Hat Satellite Certificate Tool Security Back Product Security Center Security Updates Security Advisories Red Hat CVE Database Security Labs Resources Overview Security Blog Security Measurement Severity Ratings Backporting Policies Product Signing (GPG) Keys Community Back Discussions Red Hat Enterprise Linux Red Hat Virtualization Red Hat Satellite Customer Portal Private Groups All Discussions Start a Discussion Blogs Customer Portal Red Hat Product Security Red Hat Access Labs Red Hat Insights All Blogs Events Customer Events Red Hat Summit Stories Red Hat Subscription Benefits You Asked. We Acted. Open Source Communities Subscriptions Downloads Support Cases Account Back Log In Register Red Hat Account Number: Acc
this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ mod_proxy error reading status line We're using apache mod_proxy to proxy requests to jboss servers on different hosts. We've noticed that we're getting sporadic http 502 response codes. In the apache error file, I see LOTS of these errors: [Tue Feb 26 13:55:49 2013] [error] [client 10.16.0.211] (70014)End of file found: proxy: error reading status line from remote server remotejboss-b [Tue Feb 26 13:55:49 2013] [error] [client 10.16.0.211] proxy: Error reading from remote server returned by /STRService/services/SoapToRestSOAP [Tue Feb 26 13:55:49 2013] [error] [client 10.16.0.211] no acceptable variant: /usr/local/apache2/error/HTTP_BAD_GATEWAY.html.var A bit of digging around, and I find this bug report: https://issues.apache.org/bugzilla/show_bug.cgi?id=37770This bug talks about setting 3 environment variables to resolve the issue. SetEnv force-proxy-request-1.0 1 SetEnv proxy-nokeepalive 1 SetEnv proxy-initial-not-pooled 1 My main problem is that I'm being asked to recreate this in our test environment before promoting this change to the production apache server. Recreating this has proven to be VERY cumbersome. I look at what I can do on both sides of the connection (jboss and apache) to try and recreate the issue. I see things like connection timeout and pool size, etc. Any suggestions on how I might be able to get this to occur in my test area would be GREAT!. Thanks, -mark- --------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email] Tom Evans-3 Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ Re: mod_proxy error reading status line On Wed, Feb 27, 2013 at 2:59 PM, Mark Lybarger <[hidden email]> wrote: > We're using apache mod_proxy to proxy requests to jboss servers on > different hosts. We've noticed that we're getting sporadic http 502 > response codes. In the apac