On 6/22/2016 12:45 AM, Jarno Huuskonen wrote: > On Tue, Jun 21, Shawn Heisey wrote: >> When I take down the back end server and make a request, I get the >> browser's standard unavailable page, I do not see the custom page I >> defined. Have I done something wrong? > > With "browser's standard unavail. page" do you mean IE with it's > "helpful" error messages ?
I used chrome. Didn't try other browsers. > Does your logs(w/out the "no log" option) show that "be-stg-spark-443" > returns 503 (and I guess you can compare the custom page filesize with > log entry) ? The size of the response in the logs indicate that the file IS being sent. I changed the first line of the file so it gave a 404 response instead of 503. This did NOT work in any browser I tried: Chrome, IE, and Firefox. When I changed the response code to 200, it started working in IE, but not Chrome or Firefox. Because virtually all of the clients out there are most likely using IE, this is probably good enough ... but I was really hoping that I could retain a response code indicating an error response. Do I need to do something special so that a custom page shows up in all browsers *without* returning a 200 code? This is the result in IE with the code set to 200: https://www.dropbox.com/s/qzvq1dveujtipp5/spark-unavailable-IE-200.png?dl=0 Chrome has always thought the headers were truncated and shows this: https://www.dropbox.com/s/m02bthxtnk5oiba/spark-unavailable-chrome-200.png?dl=0 When I check firebug in firefox, it shows the 200 response, but no body. Do I need additional headers in the errorfile? This is the first part of that file's contents: ============= HTTP/1.0 200 OK Cache-Control: no-cache Connection: close Content-Type: text/html <html> ============= I have verified that there is nothing on the line after the headers. On the recommendation I saw elsewhere, the file is in DOS text format, so each line ends in CRLF, not just LF. Could the line endings be the problem? Thanks, Shawn
