Your best friend for file transfer.

Fetch application logoFetch

UNIX Line Endings Not Preserved (2 posts)

This is an archived topic. The information in it is likely to be out-of-date and no longer applicable to current versions of Fetch.
  • Started 19 years ago by finishers
  • Latest reply 19 years ago from Jim Matthews
  • finishers Member

    Certain cgi files are required to have UNIX line endings by my hosting service. When files are created in BBEdit and saved selecting UNIX line breaks, they upload using Fetch 4.0.3 with DOS line breaks. (I cannot see this, but the server administrators can.) This causes the server side programming to fail giving a server side error message. The exact same file uploaded using the BBEdit ftp feature works just fine.

    There seems to be no preference setting in the upload section to specify upload textfiles using UNIX line breaks. How can files be uploaded, preserving the UNIX line breaks. What am I missing?

    Posted 19 years ago #

  • Jim Matthews Administrator

    How linebreaks are handled in uploads depends on the upload format. If a file is uploaded in Text format Fetch translates the linebreaks to the FTP standard (which happens to be the same as the DOS standard) and instructs the server to translate them to whatever the standard is on the server. If a file is uploaded in Raw Data format no translation of line endings is performed.

    It sounds like you are uploading in Text format to a Windows server; the server is using DOS line endings because that's what is standard on that platform. If you really need UNIX line endings on a Windows server you should upload in Raw Data format (which is what BBEdit does).


    Jim Matthews
    Fetch Softworks

    Posted 19 years ago #

Topic closed

This topic has been closed.