RE: parameters taintness

2008-04-22 Thread Eli Shemer
Well, Indeed it probably got stuck every time due to the locking issue but that doesn’t matter really. What I actually wanted was for a mechanism to alert me when my variables are not safe enough to work with but I could not do that. I never got any warning in the error_log and I still don’t know

Re: parameters taintness

2008-04-22 Thread Perrin Harkins
On Mon, Apr 21, 2008 at 3:48 PM, Eli Shemer <[EMAIL PROTECTED]> wrote: > eval{ > > tie %session, 'Apache::Session::MySQL', $id, > { > Handle => $dbh, > LockHandle => $dbh > }; > } > > Same behavior as I previously mentioned when the Tainted is enabled

Re: body truncated on extra reads

2008-04-22 Thread Perrin Harkins
On Tue, Apr 22, 2008 at 10:51 AM, John ORourke <[EMAIL PROTECTED]> wrote: > I'm curious - can anyone explain what actually happens internally if you > try to read more from $r->read() than specified in the Content-Length > header? What used to happen is it would hang the process forever. Not sur

Re: Best practices for returning 404/file-not-found pages inside and outside of mod_perl

2008-04-22 Thread Perrin Harkins
On Tue, Apr 22, 2008 at 2:27 PM, Mark Stosberg <[EMAIL PROTECTED]> wrote: > A. If I just set "status => 404" with CGI.pm / Apache::Registry and >return nothing, it works the first time, and then after that I >get a lot of these errors: > >"[Tue Apr 22 13:47:07 2008] [error] Can't loca

Re: Best practices for returning 404/file-not-found pages inside and outside of mod_perl

2008-04-22 Thread Mark Stosberg
I'm come to understand my 404 handling case better. Here's what I know: A. If I just set "status => 404" with CGI.pm / Apache::Registry and return nothing, it works the first time, and then after that I get a lot of these errors: "[Tue Apr 22 13:47:07 2008] [error] Can't locate SAP/Qu

body truncated on extra reads

2008-04-22 Thread John ORourke
Hi folks, I'm curious - can anyone explain what actually happens internally if you try to read more from $r->read() than specified in the Content-Length header? I noticed when trying subsequent calls to read after all bytes had been read that it truncates the buffer, which I guess is underst