Malformed multipart POST while uploading file to server

Hi

we are getting the following error while trying to upload the file on teamsite server
"
Software error:
Malformed multipart POST

For help, please send mail to the webmaster (you@yourdomain.com), giving this error message and the time and date of the error.

"

code segment from ipl file which is calling
[php]
print<<"END";

File to Upload:

END
[/php]

i am attaching fileupload.cgi

any pointers regarding this ?

Regards,
mav

Find more posts tagged with

Comments

ISCBorisB

Software error: Malformed multipart POST...

This error often means that your application died suddenly and was not able to render proper CGI-formatted output.

So - do not use "die". It's never a good idea. It's especially bad one when the execution flow expects a response like
CGI or Workflow Tasks transition. Instead of 'die' use your CGI Page as a Log of a sort. Like this...

[php]my $body ='';
if (open(whatever...)) {
# Continue...
}
else {
$body =qq(Problem opening whatever, $!);
}

print qq(Content-type: text/html; charset=utf-8\n\n

$body

);
[/php]

Adam Stoller

This error often means that your application died suddenly and was not able to render proper CGI-formatted output.

So - do not use "die". It's never a good idea. It's especially bad one when the execution flow expects a response like
CGI or Workflow Tasks transition. Instead of 'die' use your CGI Page as a Log of a sort. Like this...

I assume you meant to put the $body in between the <body> and </body> tags instead of after the latter...

Using die is okay if you use

CGI::Carp qw(fatalsToBrowser);

as that will do essentially what you are suggesting - use the browser window to display the error information.

Some would argue that it's reasonable to do that only while the code is under development - but I think that's more a matter of preference...

ISCBorisB

I assume you meant to put the $body in between the <body> and </body> tags instead of after the latter...

Using die is okay if you use
CGI::Carp qw(fatalsToBrowser);
as that will do essentially what you are suggesting - use the browser window to display the error information.

Some would argue that it's reasonable to do that only while the code is under development - but I think that's more a matter of preference...

It is certainly a matter of preference - and I completely forgot to check Carping
(You can probably say by that what my preferences are Smiley Happy

. Thanks