| commit | 4faaaf174cfc347ff660b10240eb63a2f1022003 | |
| author | Bartosz Taudul <wolf.pld@gmail.com> | |
| Sun, 15 Feb 2009 17:01:07 +0000 (15 18:01 +0100) | ||
| committer | Bartosz Taudul <wolf.pld@gmail.com> | |
| Sun, 15 Feb 2009 17:01:07 +0000 (15 18:01 +0100) | ||
| tree | 11a4bc50830e3767577a20e7db140ba2b7b45641 | treesnapshot (tar.gz zip) |
| parent | e383dd57af51c2ad1bf62620f7993dcb7a16fb72 | commitdiff |
Fix PASV reply for Firefox.
Section 4.1.2.6 of RFC 1123 (October 1989):
"The format of the 227 reply to a PASV command is not
well standardized. In particular, an FTP client cannot
assume that the parentheses shown on page 40 of RFC-959
will be present (and in fact, Figure 3 on page 43 omits
them). Therefore, a User-FTP program that interprets
the PASV reply must scan the reply for the first digit
of the host and port numbers."
How retarded is the fact that the "standard compliant", "lean and mean"
browser requires these parentheses?
Section 4.1.2.6 of RFC 1123 (October 1989):
"The format of the 227 reply to a PASV command is not
well standardized. In particular, an FTP client cannot
assume that the parentheses shown on page 40 of RFC-959
will be present (and in fact, Figure 3 on page 43 omits
them). Therefore, a User-FTP program that interprets
the PASV reply must scan the reply for the first digit
of the host and port numbers."
How retarded is the fact that the "standard compliant", "lean and mean"
browser requires these parentheses?
| Session.cpp | diffblobblamehistory |