On Thursday 21 February 2002 05:21 pm, Rick Myers wrote:
On Feb 21, 2002 at 15:23:04 -0800, Milo Hyson wrote:
On Wednesday 20 February 2002 07:55 pm, Geoffrey Young wrote:
If the redirected request needs that session
data, there's a small chance it won't be there yet.
have you
On Wednesday 20 February 2002 07:55 pm, Geoffrey Young wrote:
If the redirected request needs that session
data, there's a small chance it won't be there yet.
have you seen this? I don't recall this ever coming up before (which
doesn't mean it can't happen :)
Yes, I have seen it happen.
I moved the session cleanup phase to a PerlLogHandler and it seems to be
working, except for one small issue. Request URIs for directories (i.e. no
filename specified) don't seem to trigger the log handler. I put some
warnings in the code to trace its execution. The following is a dump
On Feb 21, 2002 at 15:23:04 -0800, Milo Hyson wrote:
On Wednesday 20 February 2002 07:55 pm, Geoffrey Young wrote:
If the redirected request needs that session
data, there's a small chance it won't be there yet.
have you seen this? I don't recall this ever coming up before (which
I just ran into a problem with my PerlFixupHandler/PerlCleanupHandler based
session manager (discussed earlier). It seems there's no guarantee that the
cleanup handler will fire before the browser receives the response from the
content handler. There's a niche case where a redirect will get to
Milo Hyson wrote:
I just ran into a problem with my PerlFixupHandler/PerlCleanupHandler based
session manager (discussed earlier). It seems there's no guarantee that the
cleanup handler will fire before the browser receives the response from the
content handler.
um, yes there is.
