Yes, "Internal Server Error" means that the server is alive and
"responding" (it's response is that for whatever reason, it was unable
to process your request).  Pound shouldn't care that there is an error
in the script, that's the job of exception handling on the server app.

You can think of it this way, Pound should be transparent, what would
happen if Pound wasn't in front of the web servers? If a normal user
received an "internal server error" message from the web server, the
server wouldn't automatically shut off and stop responding to other
valid requests.

I hope that helps.

--Alfonso

-----Original Message-----
From: Chris Sarginson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 19, 2008 10:21 AM
To: [email protected]
Subject: RE: [Pound Mailing List] A few questions

Thanks for the clarification, so if a server is responding with
"Internal Error 500" (say on a PHP script) pound would continue to
direct traffic to the server?  Is this the same with all 5xx errors?
Does pound simply check for a socket response, or  does it check for an
HTTP status?

Chris

-----Original Message-----
From: Albert [mailto:[EMAIL PROTECTED]
Sent: 19 November 2008 15:02
To: [email protected]
Subject: Re: [Pound Mailing List] A few questions

HTTP 500 level is not considered "server failure".  "Server failure" is
a state in which connection can not be established.

Chris Sarginson wrote:
> Hi guys,
>
> I've just been having a brief trawl through the Mail Archives, and
> just have a few questions that this didnt seem to answer,
>
> 1) Are HTTP 500 errors definitely treated as a failure for a server?
> 2) Is the "Emergency" directive usable as follows:
>
>            ListenHTTP
>                   Address 123.123.123.123
>                   Port    80
>                Service
>                   BackEnd
>                       Address 192.168.0.10
>                       Port    80
>                   End
>                   BackEnd
>                       Address 192.168.0.11
>                       Port    80
>                   End
>                End
>               Emergency
>                   BackEnd
>                       Address 192.168.10.10
>                       Port    80
>                   End
>                   BackEnd
>                       Address 192.168.10.11
>                       Port    80
>                   End
>                End
>                  End
>
> So that there are 2 servers available in a seperate geographic
location that are unused unless neither of the primary servers are
responding.
>
> Thanks
> Chris
>
> --
> To unsubscribe send an email with subject unsubscribe to
[EMAIL PROTECTED]
> Please contact [EMAIL PROTECTED] for questions.
>
>
>


--
To unsubscribe send an email with subject unsubscribe to [EMAIL PROTECTED]
Please contact [EMAIL PROTECTED] for questions.

--
To unsubscribe send an email with subject unsubscribe to [EMAIL PROTECTED]
Please contact [EMAIL PROTECTED] for questions.

--
This message has been scanned for viruses and dangerous content by
SecureMail, and is believed to be clean.



--
To unsubscribe send an email with subject unsubscribe to [EMAIL PROTECTED]
Please contact [EMAIL PROTECTED] for questions.

Reply via email to