mwoehlke wrote:
A.J.Mechelynck wrote:
Charles E Campbell Jr wrote:
Victor Hsieh wrote:
[...]
I know. But I just want to read the html code or so with my favoriate
editor ;) I used to do it with vim6. Actually in most case,
connecting to ftp://somewhere (when open http://somewhere) is not
gonna work.
Not if you don't have the username/password access to the site, 'tis
true.
[...]
Also not if there is no FTP server at that address.
Many FTP servers can be accessed read-only by HTTP; but most HTTP
servers have no FTP counterpart AFAIK.
"Many"? Like Victor, I would have said "most". In fact, other than
software mirrors (gnu.org and the like) I think it's pretty rare to have
a site where http and ftp are mirrors of each other (my web host, for
instance, gives me a chroot'd environment when I log into ftp, so even
though they have both, they are not symmetric). And most sites (e.g.
google.com) don't have ftp at all.
Trying ftp://somewhere when http://somewhere doesn't work *might* work
1% of the time. I would say http:// should be treated read-only, since
it almost always is, and the few cases where it isn't span a wide
variety of /ways/ in which it isn't.
Please re-read what I said. "Many FTP servers can be accessed read-only by
HTTP" (i.e., in many cases, but I didn't say "most", if FTP works, HTTP will
work too, but read-only -- these "many" FTP/HTTP servers admittedly are
usually anonymous servers like ftp.vim.org, ftp.mozilla.org, etc.) "; but most
HTTP servers have no FTP counterpart" (i.e., but if HTTP works, in most cases
FTP won't.)
Best regards,
Tony.
