[Info-vax] wrong file format

[Arne Vajhøj]

On 12/31/2020 2:09 PM, Bill Gunshannon wrote:
> On 12/31/20 1:58 PM, Phillip Helbig (undress to reply) wrote:
>> In article <rsl4jt$7ui$1 at dont-email.me>, Dave Froble
>> <davef at tsoft-inc.com> writes:
>>>> I would love to know where the original file that started this
>>>> discussion came from and how it ended up on a VMS Systems.
>>>
>>> Well, yes, Phillip is rather good at providing mysteries for us to
>>> figure out.  It sure would have been reasonable for him to lay out
>>> precisely the entire sequence of events from start to finish.
>>
>> 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.

Arne