Go
Go
Check FTP Connection and Login Status
See more FTP Examples
Demonstrates the connection-status properties ConnectVerified, LoginVerified, ConnectFailReason, and Greeting.
Background: When
Connect fails, these properties separate the possible causes: ConnectVerified shows whether the TCP connection was established at all, LoginVerified whether authentication then succeeded, and ConnectFailReason gives a numeric code pinpointing the failure — far more actionable than a generic error for distinguishing, say, an unreachable host from a bad password. The Greeting captures the server's opening banner, sometimes useful for identifying the server or its policies.Chilkat Go Downloads
success := false
ftp := chilkat.NewFtp2()
ftp.SetHostname("ftp.example.com")
ftp.SetUsername("myFtpLogin")
// Normally you would not hard-code the password in source. You should instead obtain it
// from an interactive prompt, environment variable, or a secrets vault.
ftp.SetPassword("myPassword")
success = ftp.Connect()
if success != true {
// ConnectFailReason gives a numeric code describing why Connect failed.
fmt.Println("Connect failed, reason code: ", ftp.ConnectFailReason())
fmt.Println(ftp.LastErrorText())
ftp.DisposeFtp2()
return
}
// After a successful connect, these flags report what succeeded.
fmt.Println("TCP connection verified: ", ftp.ConnectVerified())
fmt.Println("Login verified: ", ftp.LoginVerified())
// The Greeting property holds the server's initial greeting banner.
fmt.Println("Server greeting: ", ftp.Greeting())
success = ftp.Disconnect()
if success == false {
fmt.Println(ftp.LastErrorText())
ftp.DisposeFtp2()
return
}
ftp.DisposeFtp2()