codesite-noreply at google
Jun 23, 2009, 9:33 AM
Post #1 of 1
(300 views)
Permalink
|
|
Issue 503 in cherokee: 502 Bad Gateway Error
|
|
Status: New
Owner: ----
New issue 503 by plun...@areaindex.com: 502 Bad Gateway Error
http://code.google.com/p/cherokee/issues/detail?id=503
What steps will reproduce the problem?
1. Running Cherokee as reverse proxy
2. Daily we see randomly a 502 Bad Gateway error
What is the expected output? What do you see instead?
Expecting to get the normal content that is available from the one backend
server we have Cherokee in front of.
What version of the product are you using? On what operating system?
.99-19 on Ubuntu 8.04
Please provide any additional information below.
What does the 502 Bad Gateway error really mean? Can we get some sort of
error handler implemented - where and when such an error occurs Cherokee
retries processing the request a number of defineable times before failing.
Then if failing, allow configurable user setting to show a custom
error/failure type HTML page.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev
|
