Apache Mod_proxy Error Reading From Remote Server
Contents |
Start 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 apache proxy error reading from remote server returned by about Stack Overflow the company Business Learn more about hiring developers or posting ads
Apache Proxy Error Reading Status Line From Remote Server
with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system
Mod Proxy Ajp Configuration
and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top
Proxy Error Reading From Remote Server Returned By Tomcat
Proxy Error 502 “Reason: Error reading from remote server” with Apache 2.2.3 (Debian) mod_proxy and Jetty 6.1.18 up vote 46 down vote favorite 22 Apache is receiving requests at port :80 and proxying them to Jetty at port :8080 The proxy server received an invalid response from an upstream server The proxy server could not handle the request GET /. My dilemma: Everything works fine normally (fast requests, few seconds ah00898: error reading from remote server returned by 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
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. mod_proxy_http (20014)internal error: proxy: error reading status line from remote server supports HTTP/0.9, HTTP/1.0 and HTTP/1.1. It does not provide any caching abilities. If apache proxy-initial-not-pooled you want to set up a caching proxy, you might want to use the additional service 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 not enable proxying until http://serverfault.com/questions/185894/proxy-error-502-reason-error-reading-from-remote-server-with-apache-2-2-3-de 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 https://httpd.apache.org/docs/2.4/mod/mod_proxy_http.html 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 what the Client sent to the proxy. It ensures compatibility when pro
Proxy Error The proxy server received an invalid response https://confluence.atlassian.com/confkb/proxy-error-when-viewing-the-content-indexing-page-389777939.html from an upstream server. The proxy server could not handle the request GET /admin/search-indexes.action. Reason: Error reading from remote server Apache/2.2.15 (CentOS) Server at confluence.com Port 80 Cause This error message triggered when an SSL connection is configured from the browser to Apache, and error reading Apache does a reverse proxy to your Tomcat server. Internet Explorersends the wrong host information in an SSL connection and confuses Apache VirtualHosts. In short, the server name presented is that of the reverse DNS resolution of the IP, not the one in the URL. from remote server Workaround There are three workarounds for this issue: Remove the reverse proxy Make a configuration where there's only one IP address per SSL virtual hosts/server name1 server name == 1 IP address == 1 certificate == 1 Apache Virtual Host Use a different browser References: Server Name Indication Was this helpful? Yes No Thanks for your feedback! Why was this unhelpful? It wasn't accurate It wasn't clear It wasn't relevant Submit feedback Cancel Have a question about this article? See questions about this article Powered by Confluence and Scroll Viewport Atlassian Support Ask the community Provide product feedback Contact technical support Atlassian Privacy Policy Terms of use Security Copyright © 2016 Atlassian Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.