Proxy Error Reading From Remote Server Returned By Iis
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
(20014)internal Error: Proxy: Error Reading Status Line From Remote Server
Learn more about Stack Overflow the company Business Learn more about hiring developers apache error reading status line from remote server or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question ah00898: error reading from remote server and answer site for system 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
Proxy-initial-not-pooled
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 response from an upstream server The proxy server could not handle the request GET /. My dilemma:
The Proxy Server Received An Invalid Response From An Upstream Server. Apache
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
[x] First Last Prev Next This bug is not in your last search results. Bug37770 (104)connection reset by peer: proxy: error reading status line from remote server - proxy: error reading status line from remote server (null) Summary:
Setenv Proxy-nokeepalive 1
proxy: error reading status line from remote server (null) Status: REOPENED Product: Apache httpd-2 Classification: Unclassified Component: error reading status line from remote server localhost 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 Duplicates: 32731 37876 http://serverfault.com/questions/185894/proxy-error-502-reason-error-reading-from-remote-server-with-apache-2-2-3-de 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: 2016-10-09 10:57 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 paul.kmiec ronn.chinowutthichai rvandolson suresh.pagadala https://bz.apache.org/bugzilla/show_bug.cgi?id=37770 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 reading from remote server returned by /xxxx.gif, referer: http://portail.polen.xxxx
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta http://stackoverflow.com/questions/19851192/mod-proxy-502-proxy-error-when-upload-a-file Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack https://bugs.debian.org/410331 Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, error reading helping each other. Join them; it only takes a minute: Sign up mod_proxy 502 Proxy Error when upload a file up vote 1 down vote favorite 1 I'm trying to configure the following environment: a VPS running apache and mod_proxy to proxy another server running at home (the backend). I'm able to download files but when I try from remote server to upload files the POST request fails with this error: Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request POST /upload/upload.php. Reason: Error reading from remote server What I don't understand is why it works for files as low as 500 bytes. And it does quickly! However, when I try to upload a tiny 4kb file, it takes forever until the error is reached. As expected, the upload works flawlessly when the backend is accessed directly, without the VPS. I tried many configurations for both sides, also tried to increase the timeout but I don't think this is the way to go. The backend has mod_access installed and it doesn't log anything when the file upload fails. The apache logs the following: [Thu Nov 07 22:26:03.044309 2013] [proxy_http:error] [pid 9173] (70007)The timeout specified has expired: [client 177.148.252.99:54097] AH01102: error reading status line from remote server myhome.com, referer: http://frontend.com/upload/ [Thu Nov 07 22:26:03.044423 2013] [proxy:error] [pid 9173] [client 177.148.252.
apache2 is src:apache2. Reported by: "Kris Boutilier"