Hi folks,
I'm running into a text file problem, wanted to know if anyone could help.
Basically, I have some UNIX shell scripts that run a PL/SQL program. At the end of the process, it outputs several text files, which are then sent to a vendor's HTTPS site using cURL.
During testing, most of the files were sent manually, and no problems were experienced. However, once we started sending the files in an automated fashion, it seems that the different text formats of UNIX and windows has started causing problems.
Basically, when we sent the files manually from Windows machines, the files had both a CR and a LF at the end of each line, but now they only have a CR. (I'm not 100% certain that that's accurate - I'm trying to confirm right now.)
But, the idea is right - it has to do with UNIX and DOS-format text files treating end-of-line differently.
Does anyone know, is there any way I can send these files from the UNIX box using cURL, but not have them arrive in this UNIX text format?
Thanks,
Steve
I'm running into a text file problem, wanted to know if anyone could help.
Basically, I have some UNIX shell scripts that run a PL/SQL program. At the end of the process, it outputs several text files, which are then sent to a vendor's HTTPS site using cURL.
During testing, most of the files were sent manually, and no problems were experienced. However, once we started sending the files in an automated fashion, it seems that the different text formats of UNIX and windows has started causing problems.
Basically, when we sent the files manually from Windows machines, the files had both a CR and a LF at the end of each line, but now they only have a CR. (I'm not 100% certain that that's accurate - I'm trying to confirm right now.)
But, the idea is right - it has to do with UNIX and DOS-format text files treating end-of-line differently.
Does anyone know, is there any way I can send these files from the UNIX box using cURL, but not have them arrive in this UNIX text format?
Thanks,
Steve