[Info-vax] wrong file format

Dave Froble davef at tsoft-inc.com
Thu Dec 31 20:13:08 EST 2020


On 12/31/2020 3:05 PM, Arne Vajhøj wrote:
> 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.

Most of the "optional" HTTP headers are just that, optional, and I've 
seen way too many headers that were sorely lacking in sufficient header 
data.



-- 
David Froble                       Tel: 724-529-0450
Dave Froble Enterprises, Inc.      E-Mail: davef at tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA  15486



More information about the Info-vax mailing list