CRLF question

Advertisement

mohanr
Joined:
Posts:
2

CRLF question

Even in binary mode the server admin. is reporting that '0D 0A' is present in the file even though '0D' is removed here with a hex editor. What could go wrong while transmitting the file ? Is this a known issue ?

I thought that binary mode does not touch the file.

Reply with quote

Advertisement

martin
Site Admin
martin avatar
Joined:
Posts:
29,302
Location:
Prague, Czechia

Re: CRLF question

mohanr wrote:

I thought that binary mode does not touch the file.
Sure it does not. So if the file is indeed modified, there has to be another problem.

Please post a full log file showing the problem.

To generate log file, enable logging, log in to your server and do the operation and only the operation that causes the error. For posting extensive logs you may use pastebin or similar application. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you may email it to me. You will find my address (if you log in) in my forum profile. Please include link back to this topic in your email. Also note in this topic that you have emailed the log.

_________________
Martin Prikryl

Reply with quote

mohanr
Joined:
Posts:
2

Re: CRLF question

I have sent a mail with Logs. I don't see '0D' in the bytes printed in the logs. So it seems to some other problem.

A file generated using Java can have a eof. A CTRL Z( EOF ) at the end of file is also reported by the server admin. Even this is not seen in the logs. I think it is 1A

Reply with quote

Guest

CRLF question

It is funny that even though the WinSCP logs show the bytes without the 0D character the linux admin is still complaining.

Reply with quote

Advertisement

You can post new topics in this forum