I think antirice is correct. This would have been caught if you been using strict, but with strict in place you are also unable to use the filename returned by param() as a filehandle. You probably want to consider using the upload() method instead:

#!/usr/bin/perl -w use strict; use CGI qw(:standard); use CGI::Carp qw(fatalsToBrowser); use File::Basename; my $fh = upload('userfile'); my $filename = param('userfile'); my ( undef, undef, $ext ) = fileparse($filename, '\.\w+$'); $filename = time() . $ext; open OUTFILE, "> /tmp/$filename" or die "/tmp/$filename - $!\n"; binmode OUTFILE; binmode $fh; print header('text/html'), start_html(), p("filename : $filename (saved in /tmp)"); while (<$fh>) { print OUTFILE $_; } print end_html();
/J\

In reply to Re: file from multipart form not being written to the server! by gellyfish
in thread file from multipart form not being written to the server! by AztecMonkey

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.