title: SFTP Upload in "ASCII" Mode
body: <p>I have a simple text file that I am uploading from a windows platform to a Unix server using SFTP (Client: FireFTP). I have noticed that when uploading using SFTP rather than plain FTP, the file is forced to upload in "Binary" mode rather than in "ASCII". </p>
  
  <p>Anyone aware of the reasoning behind enforcing the transfer method? Normally this would not matter but I am parsing this file (char by char) on the server and the hanging ^M that is left on the file when uploaded in "Binary" causes an issue with my parser. </p>
  
  <p><em>Yes, I am changing the parser to handle this but, I am mainly interested in why SFTP forces the upload to occur in "binary" rather than "ASCII?</em></p>
  
  <h2>Is it a security vulnerability that I am not understanding perhaps?</h2>
  
  <h2>Is this a matter of what SFTP protocol version the client is using (In this case FireFTP)?</h2>
  
  <h2>EDIT:</h2>
  
  <p>If "ASCII" is no longer an option with modern SFTP, is it simply "accepted" that when transferring a file from Windows -> Unix that you will have the additional CR (^M) leftover throughout the file on the Unix server where previously contained the standard Windows(CRLF)?</p>
  
  <p>Thanks for the guidance</p>