[Info-vax] wrong file format
Bill Gunshannon
bill.gunshannon at gmail.com
Thu Dec 31 22:59:03 EST 2020
On 12/31/20 5:16 PM, Phillip Helbig (undress to reply) wrote:
> In article <rslath$1iso$1 at gioia.aioe.org>, =?UTF-8?Q?Arne_Vajhøj?=
> <arne at vajhoej.dk> writes:
>
>>>> That would take more time than it is worth. Suffice it to say that they
>>>> were uploaded via a shaky http connection.
>>>
>>> Believe it or not, that goes a long way towards explaining what
>>> happened and what you got. HTTP does not have a concept of
>>> ASCII/BINARY. Transferring "text" files from none VMS systems
>>> to VMS systems using HTTP is bound to result in at least the
>>> CR+LF|LF+CR|CR|LF problem and, depending on the sending system
>>> even stranger results are possible,
>>
>> HTTP has the Content-Type header.
>>
>> If that is text/plain or text/something then the client
>> knows it is text.
>>
>> And a VMS client can treat it appropriately including
>> writing a file with rfm:var.
>
> The question is why sometimes it worked but occasionally not.
>
I would be looking at the receiving client for the answer to that.
bill
More information about the Info-vax
mailing list