comment on

At first guess I'd say Net::FTP could be using chomp?

Let's say, you're on a Win32 machine, chomp is designed to remove the last 2 characters (CR,LF) right? Then say you feed a unix-formatted file through, then it is conceivable that chomp does the "wrong thing" and takes the last character of text from each line as well as the LF.

Personally I never use chomp. Instead I prefer to correct for line endings by doing the following:

  $line =~ s/(\r\n|\n\r|\r|\n)//;
[download]

The regular expression forces a test for CR,LF and vice-versa before considering that the line may end with just a single LF. Portable across operating systems and text file formats.

It seems in this situation you are safest with just sending in binary format, and failing that maybe try hacking the source of Net::FTP yourself?

In reply to Re: Net::FTP and corrupted uploads by monarch
in thread Net::FTP and corrupted uploads by wfsp

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Clear questions and runnable code get the best and fastest answer
	PerlMonks