What is the standard way to determine whether a user is indeed logged in to
a site and online right then? I have a web app where users log in and get a
cookie. Part of it is the sessin cookie which expires at the close of the
session, and part of it is a longer lasting authentication cookie. Am I
You are correct--I get that error even after I have disabled mo_rewrite. It
must be something else.
Amiri
Matus UHLAR - fantomas wrote:
amiribarksdale [EMAIL PROTECTED] writes:
About the only strange thing in my debug-level error logs is
(32)Broken pipe: client stopped connection
Ben Ricker wrote:
Ahhh. Good point. I spaced the rewrite part. You are right: looking at
any rewrites is a candidate since it is very unlikely to catch a
healthy rewrite intact with a reload.
Well, I turned off rewrites, so we'll see what happens.
Amiri
--
View this message in
Krist van Besien wrote:
What are you using mod_perl for? Are you producing any dynamically
generated content? Could be that apache itself is waiting for some
script or module to finish...
Of course that's what I'm using it for. It's possible, but not likely, that
Apache is actually
Ben Ricker wrote:
One issue is likely keep-alives. One issue with graphics is that each
one is a separate request requiring a separate SSL connection (unless
the KeepAlive is set to a reasonable value (I think we set ours to
10k). Check out here:
Hello folks:
I have newly built web server with very little load, and beginning several
minutes after a server restart, it just hangs for no good reason. I click a
page, and the browser just waits. The request comes up in my access logs,
but top shows no httpd activity. No new children seem to
I'm not using CGI--just mod_perl. The request that hits the access log is
just for the bare html page--nothing else on it or in it. No images or
anything. The request that hits the logs is for the page, and then the
infinite wait begins. Sometimes after it begins to load, it doesn't get all
the
About the only strange thing in my debug-level error logs is
(32)Broken pipe: client stopped connection before rwrite completed
This happens when I try to reload a page in the midst of a wait.
Amiri
--
View this message in context:
I have turned off ssl by just commenting out that part of my httpd.conf, and
while I still get the wait with no other traffic on the server, the page
does seem to load--within 10 or 15 seconds, as opposed to a minute or
longer.
So, if this is indicative of some problem with ssl, how do I go
