Connecting to Sites 

CuteFTP takes advantage of the keep alive header (as defined in RFC 2068 & 2616) which 

keeps the session open during multiple transactions, saving the user considerable time and 

bandwidth.  

Note:  

The Web server must support basic authentication as described in RFC 

1945 . Because of the way 

authentication works, the server may challenge the client: with a WWW 

Authenticate request. The client responds with: Authorization: Basic 

. Most Web Servers support basic 

authentication but require intervention on the site operator s behalf to set 

it up because it is server specific. Various existing sites employ other 

authentication schemes, such as NTLM or those found in ASP or 

JavaScripts, and are not supported by CuteFTP.  

Connecting to secure sites 

You can make secure connections and transfers with FTPS (SSL/TLS), SF P

T  (SSH2), 

HTTPS (SSL), and standard FTP with One Time Password authentication. 

T

O CONNECT TO AN 

FTPS (SSL/TLS) 

SITE

1.  From the menu, select File > New > FTPS (SSL) Site.  

2. The 

Site Properties dialog box appears.  

3.  Type in the host, user n

  ame and password.  

4. Select 

the 

Type tab.  

5. In 

the 

Protocol list, choose FTP with TLS/SSL (Implicit encryption), or FTP 

with TLS/SSL (Explicit encryption), or FTP with TLS/SSL (AUTH TLS   

Explicit). The appropriate port will be s l

e ected. Certain servers support only one of 

the above SSL connection mechanisms.  

6. Select 

Connect or OK. 

T

O CONNECT TO AN 

SSH2 (SFTP2) 

SITE

1.  From the menu, select File > New > SFTP (SSH2) Site. 

2. The 

Site Properties dialog box appears.  

3.  Type in the host, user n m

a e and password. 

4. Select 

Connect or OK. 

T

O CONNECT TO AN 

HTTPS 

SITE

1.  From the menu, select File > New > HTTPS (SSL) Site.  

2. The 

Site Properties dialog box appears.  

31