blob: fb59e9870d25d695365a3080c0dcf6ea5b16bdf2 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
|
Network Working Group Robert T. Braden
Request for Comments: 571 UCLA/CCN
NIC #18974 November 15, 1973
TENEX FTP PROBLEM
Tenex users of FTP should beware of a problem in the current Tenex
implementation which is likely to cause incorrect results when
transferring files to a non-Tenex site. Some Tenex programs create
an ASCII US (Unit Separator) character as an end-of-line indicator,
instead of CR LF. The current Tenex FTP user implementation passes
these US characters over the Network instead of translating them to
CR LF as required by FTP protocol. If the recipient is not a Tenex,
he will not do anything special with these US characters and the line
spacing will be lost. In the case of sending to CCN, we will treat it
as a very long logical record and fold it into successive 360
records.
A circumvention is to pass the Tenex file through some Tenex program
that does the necessary conversion before sending it over the
Network. We know that TECO will remove US's; there are probably
other means. Loading and saving the file with TECO will replace all
US's with CR LF sequences.
[ This RFC was put into machine readable form for entry ]
[ into the online RFC archives by Katsunori Tanaka 4/99 ]
Braden [Page 1]
^L
|
