On Wed, 4 Oct 2000 [EMAIL PROTECTED] wrote:
I have an authentication scheme which checks every request for a valid
cookie, and if your session has timed out redirects to a login page. After
logging in, the request is resubmitted as a GET. This works great except
when the original post is
On Thu, 5 Oct 2000, Sean D. Cook wrote:
sub destroySession {
delete session or mark for deletion
}
If you manage this with one of the IPC::Share* modules and don't get
munged shared memory segment errors, I'd like to know how.
Cheers,
--
steven
On: Wed, 04 Oct 2000 15:24:27 PDT [EMAIL PROTECTED] wrote:
I was thinking about saving the posted data to a temporary file and
reading it back in after the login succeeds, but this seems messy and
error-prone. Has anyone else had this problem? Are there any modules
(maybe session mgmt stuff?)
Kip Cranford wrote:
I did this because in my system, I routinely need to allow file uploads
of 100MB or more. This is too unwieldy, IMO, to upload, store,
retrieve, etc. So far, this has worked like a charm.
Dare I ask what that 100MB consists of? That's a lot of uploaded data...
:-)
--
On: Thu, 05 Oct 2000 09:45:30 EDT Drew Taylor wrote:
Dare I ask what that 100MB consists of? That's a lot of uploaded data...
:-)
Pr0n, mostly :)
Seriously, though, most of the information consists of CAD binary data
(I work in the automotive industry), so we're talking large parts,
I have an authentication scheme which checks every request for a valid
cookie, and if your session has timed out redirects to a login page. After
logging in, the request is resubmitted as a GET. This works great except
when the original post is large--the redirect URL gets way too long (10K
or
