Serv-U offers two methods of access that do not require any end-user client software or configuration. The most convenient option is the Serv-U Web Client and FTP Voyager JV, which are both launched by configuring the Serv-U HTTP listener. These web-based FTP clients allow users to browse to a standard web page and either access all of their directories and files via an easy-to-navigate web site (Web Client) or launch a fully functional FTP Client which is loaded on-demand from Serv-U and offers extended functionality, similar to a normal FTP client (FTP Voyager JV, available as an add-on to Serv-U). The alternative is to use the FTP client that comes built into most web browsers - because implementations vary, RhinoSoft.com recommends the Web Client and FTP Voyager to provide a consistent, reliable experience to your clients.

Configuring The HTTP/HTTPS Listener

The Serv-U HTTP and HTTPS Listeners are responsible for providing clients with access to the Web Client and FTP Voyager JV (if installed). These two listeners are configured the same as any of the other listeners in Serv-U - to add the HTTP or HTTPS listeners to your server, follow the steps below:

• Navigate to Domain Details | Listeners
• Select "Add", and then select "HTTP" (or HTTPS for secured HTTP)

  

• If necessary, select the IP the listener should bind to, then select "Save"

Once users log on to the HTTP listener by browsing to your domain name or IP address, they will be able to log on using the Serv-U interface (demo available online at the Serv-U Demo Server). If their Default Web Client has not already been specified and the FTP Voyager JV has been purchased, they will be prompted to select whether they wish to use the Web Client or FTP Voyager JV. Which is the better choice depends on the needs of the user and whether that user has Java installed, which is required for FTP Voyager JV. If Java is not installed and cannot be installed, the Web Client must be used.

NOTE 1: It is important to note that if the server that Serv-U is installed on is also running a web server on port 80 (which is the web server default), Serv-U's HTTP Listener and the web server may interfere with each other. This can be resolved by configuring the HTTP listener to use a different port (such as 8080, requiring users to connect to your Serv-U server at http://www.yourdomain.com:8080), or assigning multiple IP addresses to your server and specifying one IP address for Serv-U to use and a different IP address for the web server to use. NOTE 2: If Serv-U is installed on a network which uses NAT and that same network is also running a web server, the network's router is likely already forwarding port 80 to the web server and will not be able to specifically send Serv-U requests to Serv-U. In this case, Serv-U MUST run on a different port number such as 8080 and the router must forward port 8080 to Serv-U. NOTE 3: In order for the HTTPS listener to operate, an SSL certificate must be configured in Domain Limits & Settings | Encryption.

Logging On Using A Browser FTP Interface

Most web browsers include a built-in FTP client that allows users to connect to FTP servers and transfer files. This requires using a specific URL that is interpreted by your web browser, allowing it to respond to your request. The web browser is fully responsible for the implementation; it is not Serv-U specific, but rather works with all FTP servers. This format allows most browsers to connect to the Serv-U FTP listener. The format is as follows:

ftp://userid:password@site:port

• userid - the user id to be used for the connection
• password - the password used in conjunction with the userid
• site - the FTP server name or IP address
• port - if the port number is not 21, specify the port number here

Using The "Log On" Option

Serv-U 4.1.0.3 and higher allows a "Login As" box to appear in a web browser if no user name and password are directly applied to the URL.

In Serv-U 4.1.0.2 and lower the user name and password must be applied in the full format described above.