On Wed, Mar 5, 2008 at 10:37 AM, <[EMAIL PROTECTED]> wrote:
> 502's show up when you have more connections from the front end to the
> back end that it can service.
Just to expand on that a little, you should start by checking for
simple things like whether your machine was going into swap or ge
Jeremy Wall wrote:
I currently use Apache2::Reload on my development environments. However it's
usefulness has been spotty particularly on win32 environments. Someone
recently recommended Module::Refresh to me as an alternative.
FWIW, I have not had much luck with Apache2::Reload in my develop
502's show up when you have more connections from the front end to the
back end that it can service. The proxy server has a timeout [1], and
if it doesn't get a response within that time frame you get a 502.
You can create a custom error document on your front end for 502's to
make them a
Hi folks,
Slightly OT but hopefully someone on here has had similar experience.
I've got a site with fairly heavy traffic and a light/heavy apache
setup. Occasionally the back-end servers seem to get swamped and
suddenly every request from the front end starts getting a 502 proxy
timeout un
Peter Wood wrote:
[..]
I've had other experiences where I found a module that already did
something I was trying to do, but this is the first time I've started
writing one with the exact same name. :-)
If you write further modules, to avoid name clashes you might also want
to avoid names such
Ironically, I had already started writing my own class called
Apache::Filter (which I had intended to implement within each CGI
script), completely unaware that a class with that name already existed,
and did exactly what I was looking for. This will be much better and
save lots of time.
I've had
