This is a discussion on handling an error response 'HTTP 1.1 599 Internal Error' within the Apache Web Server forums, part of the Web Server and Related Forums category; Hi All, I have an application that returns an error page that is ugly and am trying to get apache ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Hi All,
I have an application that returns an error page that is ugly and am trying to get apache to replace it with something a little nicer. The page comes from an app server which is accessed via reverse proxy ( ProxyPassReverse ). The error page's headers shows the HTTP status '599 Internal Error'. I guess they just made this code up! I'm running Apache/2.0.55 and when I add 'ErrorDocument 599 /error/ 599.html' to the conf it restarts erroring with 'Unsupported HTTP response code 599' Any ideas on how to deal with this response and show a custom error page? Thanks in advance, Cliff. |
|
|||
|
On Sep 11, 3:28 pm, cliffwea...@gmail.com wrote:
> Hi All, > > I have an application that returns an error page that is ugly and am > trying to get apache to replace it with something a little nicer. > > The page comes from an app server which is accessed via reverse proxy > ( ProxyPassReverse ). The error page's headers shows the HTTP status > '599 Internal Error'. I guess they just made this code up! > > I'm running Apache/2.0.55 and when I add 'ErrorDocument 599 /error/ > 599.html' to the conf it restarts erroring with 'Unsupported HTTP > response code 599' > > Any ideas on how to deal with this response and show a custom error > page? > > Thanks in advance, > > Cliff. rewrite this response off to another page you can create. |
| Thread Tools | |
| Display Modes | |
|
|