Configuring the HTTP Server - FTP Server | Main configuring page

The HTTP Server has 14 main settings windows. Initially the server will run on the defaults. If all you want to do is simply browse web pages, then WebServUSB's default settings are sufficient.

The Main HTTP Server Window

HTTP
If you are going to have all your websites in a different directory than 'docs' it has to be set here in the Virtual Root box. Click the [...] button and browse to the directory required. Until you're familiar with the many features of WebServUSB we recommend leaving the settings as they are.

Threads
For a "typical" user, the defaults should be fine. Each request that comes to the WebServUSB gets its own thread. So if you have a very high volume site, then you may need to increase the number of allowed threads. The 'Thread Cache Pool' is the number of threads that will be "stored". Usually a thread is created for each request. But the Thread Cache allows threads, once they are finished, to be cached, and reused again. This saves the overhead of creating and destroying threads. 'Maximum Threads' are the most threads that WebServUSB will create to service requests. If it were set to 8 (the default) and there were 9 simultaneous requests, then one thread would be delayed, and it would wait until one of the other threads had completed its task.

The default numbers in the threads section will usually work for most users. For a regular request of an HTML page, the request will very short (> 50 milliseconds) The only case where it might not, is if the user is doing CGI requests, and the CGI program takes a long time to finish (like if they are doing database access). Basically, leave these settings alone unless the WebServUSB seems to stop responding to requests periodically. If it does, try raising the MAX Threads and see if it helps.

Create Threads at startup  It does just that. It pre-populates the Thread Cache with the appropriate number of threads at startup instead of on demand.

• Thread Cache Pool Size: set at size you want
• Maximum Threads: set at how many threads you want
• Create threads at startup: click box to enable
• Priority: click the radio button of the priority you wish to set

Options
'Never Send 304 Response' was because browsers don't always do what they are supposed to. A 304 response basically means "The file you requested hasn't changed since last time you requested it". All the info is based on timestamps that are passed. So the file is not returned, just this empty response. The browser is then supposed to load the file that it has cached. It is a bandwidth saving method. The problem is that sometimes browsers will send the request, the WebServUSB will respond with a 304 - and then the browser doesn't display it's cached file. So the effect is that the users thinks that the WebServUSB is broken because it didn't return anything. This option was added so that if a users is getting a blank page (because the browser isn't displaying its cached file) they can check this, the file will be sent so that the browser displays it correctly.

Check the 'Never Send 304 Response' box if you don't want 304 responses.

The reemainder of the Category settings
(will appear in popup windows)

• Alias
• Cache
• Directory Browsing
• Error Redirection
• IP Security
• ISAPI/CGI
• Logging
• MIME
• Network
• PHP
• Realm Security
• Statistics
• SSI

Configure the FTP Server next.