Hi,
you may find this useful :
503 Service Unavailable
The server is currently unable to handle the request due to a
temporary overloading or maintenance of the server. The implication is
that this is a temporary condition which will be alleviated after some
delay. If known, the length of the delay MAY be indicated in a Retry-
After header. If no Retry-After is given, the client SHOULD handle the
response as it would for a 500 response.
Note: The existence of the 503 status code does not imply that a
server must use it when becoming overloaded. Some servers may
wish
to simply refuse the connection.
(found on http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html)
Cheers,
Guillaume
On 19 nov, 15:37, Nei Rauni Santos <[email protected]> wrote:
> Hi Guys,
>
> I have many symfony's websites in a single server and I'm thinking to add a
> filter to monitor the load average of the server and when it's too hight
> like 60.0 the symfony return 503 service unavailable.
>
> I have others monitoring to prevent this situation, but it's a plus on the
> application.
>
> Do you think it's a good idea? The best way to do that is on filters system?
>
> I hope to receive some ideas about that.
>
> Thank you,
>
> --
> Nei Rauni Santos
>
> http://www.linkedin.com/in/neiraunisantoshttp://www.facebook.com/nei.santoshttp://www.twitter.com/nraunihttp://blog.inuar.com
>
> Curitiba - Paraná
> +55 41 85020985
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
