You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by "Veaceslav Puscasu (personal)" <vi...@compudava.com> on 2002/04/26 15:55:37 UTC
Custom 502 proxy error page problem
Hi list,
I use Apache server as a proxy. All requests are redirected to the Orion App Server. When Orion is down a get 502 Proxy Error. Instead of this error I would like that the users to see my custom error page. To do this in httpd.conf file I put this:
ErrorDocument 502 / maintain.html (maintain.html file is located in my ServerRoot directory.)
But in this case I receive
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /.
Reason: Could not connect to remote machine: Connection refused
Additionally, a 502 Bad Gateway error was encountered while trying to use an ErrorDocument to handle the request.
Any help will be much appreciated.
Alex.
Re: Custom 502 proxy error page problem
Posted by "Veaceslav Puscasu (personal)" <vi...@compudava.com>.
It is a typo...
----- Original Message -----
From: "Owen Boyle" <ob...@bourse.ch>
To: <us...@httpd.apache.org>
Sent: Friday, April 26, 2002 5:09 PM
Subject: Re: Custom 502 proxy error page problem
> > ErrorDocument 502 / maintain.html
>
> Is that a typo or do you really have a space between "/" and
> "maintain.."? If so, remove it!
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: Custom 502 proxy error page problem
Posted by Owen Boyle <ob...@bourse.ch>.
> ErrorDocument 502 / maintain.html
Is that a typo or do you really have a space between "/" and
"maintain.."? If so, remove it!
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
BUG in apache 1.3.24 mod_proxy?????
Posted by Scaglione Ermanno <sc...@starnetone.de>.
I think I made some confusion with the versions numbers .. here it is again
with the right versions:
We are using apache 1.3.23 with mod_proxy to serve (ProxyPass) pages from a
couple of server (apache 1.3.23) doing php and mysql. Recently I tried to
upgrade the frontends to 1.3.24, I simply copied the configuration from the
old server to the new server and corrected all the paths (no directive has
changed I suppose). I noticed immediatly that something strange was going
on, all the local virtual web servers (on the frontend) were working as
usual, 50% of the virtual web server that uses the ProxyPass directive
weren't no longer working. That was really strange is that other sites, same
frontend and backend, were working correctly while other weren't, I suppose
1.3.24 introduced a bug in the mod_proxy code.
The problem happens only when I try to access using a proxy cache (squid or
Cisco) a virtual web server implemented with a ProxyPass directive:
PC ----> squid ------> frontend 1.3.24 -----> backend
doesn't work
PC ----> squid ------> frontend 1.3.23 -----> backend
works
PC ----> frontend -----> backend
works
PC ----> backend
works
That is accessing the web server directly or only through mod_proxy
everything works, if there is a proxy cache in between (I tried several)
some virtual web server (in my case all based on PHP 4.0.6) behave
erratically, in some cases instead of the html the client recieves only some
random numbers or letters, in others the random numbers or letter replaces
an image or only parts of the page. In all cases disabling the local proxy
cache solves the problem, that is of course a non solution considering that
expecially here in Germany many ISP are doing transparent proxying. I found
nothing unusual on the logs (backend, frontend and one squid).
I'm intrested in updating to the 1.3.24 version because of the new features
in mod_proxy considering that we are using it a lot, it looks like maybe it
is better to wait a little .....
Somebody has an idea about what is going on or experiencing similar problems
after an upgrade to 1.3.24?
Please CC answers to me too.
BUG in apache 1.3.24 mod_proxy?????
Posted by Scaglione Ermanno <sc...@starnetone.de>.
We are using apache 1.2.23 with mod_proxy to serve (ProxyPass) pages from a
couple of server (apache 1.3.23) doing php and mysql. Recently I tried to
upgrade the frontends to 1.3.24, I simply copied the configuration from the
old server to the new server and corrected all the paths (no directive has
changed I suppose). I noticed immediatly that something strange was going
on, all the local virtual web servers (on the frontend) were working as
usual, 50% of the virtual web server that uses the ProxyPass directive
weren't no longer working. That was really strange is that other sites, same
frontend and backend, were working correctly while other weren't, I suppose
1.2.24 introduced a bug in the mod_proxy code.
The problem happens only when I try to access using a proxy cache (squid or
Cisco) a virtual web server implemented with a ProxyPass directive:
PC ----> squid ------> frontend 1.3.24 -----> backend
doesn't work
PC ----> squid ------> frontend 1.3.23 -----> backend
works
PC ----> frontend -----> backend
works
PC ----> backend
works
That is accessing the web server directly or only through mod_proxy
everything works, if there is a proxy cache in between (I tried several)
some virtual web server (in my case all based on PHP 4.0.6) behave
erratically, in some cases instead of the html the client recieves only some
random numbers or letters, in others the random numbers or letter replaces
an image or only parts of the page. In all cases disabling the local proxy
cache solves the problem, that is of course a non solution considering that
expecially here in Germany many ISP are doing transparent proxying. I found
nothing unusual on the logs (backend, frontend and one squid).
I'm intrested in updating to the 1.3.24 version because of the new features
in mod_proxy considering that we are using it a lot, it looks like maybe it
is better to wait a little .....
Somebody has an idea about what is going on or experiencing similar problems
after an upgrade to 1.3.24?
Please CC answers to me too.