>$obj, as you use it above, is intented if need an second object with
>different inherece hierachie. Also you can store data in $obj, it is only
>available to the pages that have access to $obj, so you have to store $obj
>somewhere, e.g. in $req -> {obj}.
I wonder I do not understand
can you give
Hi--
I have been doing final security checks before bringing a website live --
making sure that users can't manually enter post data to see things they
shouldn't. My employer is naturally curious about any security issues that
tend to aflict embperl/mod_perl/cgi. While we have followed common sen
that worked, thank you!
Gerhard
On Wed, 1 Aug 2001, Gerald Richter wrote:
> >
> > [Tue Jul 31 18:05:38 2001] [error] [31481]ERR: 44: Line 1: Setup of
> > CGI.pm failed: Malformed multipart POST
> >
>
> That is handled by CGI.pm and the error message is from CGI.pm, so maybe
> upgrading CGI.
> Embperl 1.3.1
You should also upgrade Embperl to 1.3.3, because 1.3.3 handles errors in
CGI.pm much better
Gerald
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
>
> [Tue Jul 31 18:05:38 2001] [error] [31481]ERR: 44: Line 1: Setup of
> CGI.pm failed: Malformed multipart POST
>
That is handled by CGI.pm and the error message is from CGI.pm, so maybe
upgrading CGI.pm to a newer version may help...
Let me know if this solves your problem
Gerald
hi all,
when uploading a file using our Embperl script
with a certain browser version (sorry i can't tell which)
the server-request quits with:
[Tue Jul 31 18:05:38 2001] [error] [31481]ERR: 44: Line 1: Setup of
CGI.pm failed: Malformed multipart POST
it works fine with all our (NS- & IE-) bro
