Re: "errorfile 503" doesn't appear to be working

On 6/22/2016 7:41 PM, Michael Ezzell wrote: > On Jun 22, 2016 7:06 PM, "Shawn Heisey" > wrote: > > > > 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

Re: "errorfile 503" doesn't appear to be working

My previous post included a couple of spurious spaces after a couple of the header values. Corrected here: HTTP/1.0 503 Service Unavailable[0d][0a]Content-Type: text/html[0d][0a]Cache-Control: no-cache[0d][0a]Connection: close[0d][0a][0d][0a]... Side note: be sure your body is at least 512

Re: "errorfile 503" doesn't appear to be working

On Jun 22, 2016 7:06 PM, "Shawn Heisey" wrote: > > 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?

Re: "errorfile 503" doesn't appear to be working

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

Re: "errorfile 503" doesn't appear to be working

Hi, 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"

"errorfile 503" doesn't appear to be working

This is the backend config: backend be-stg-spark-443 description Back end for spark stg ssl errorfile 503 /etc/haproxy/pages/spark-error.http no log log 127.0.0.1 local0 notice err server palazzo 10.100.2.17:443 ssl track chk-liferay-stg-443/palazzo The