User manual
Table Of Contents
- Web Technologies Administration
- Contents
- Web Technologies Overview
- Managing Web Technologies
- Managing Websites
- Using Server Admin to Manage Websites
- Changing the Access Port for a Website
- Improving Performance of Static Websites (PerformanceCache)
- Enabling Access and Error Logs for a Website
- Setting Up Directory Listing for a Website
- Connecting to Your Website
- Enabling WebDAV on Websites
- Enabling a Common Gateway Interface (CGI) Script
- Enabling Server Side Includes (SSI)
- Viewing Website Settings
- Setting Server Responses to MIME Types and ContentHandlers
- Enabling SSL
- Enabling PHP
- User Content on Websites
- WebMail
- Secure Sockets Layer (SSL)
- Working With Open-Source Applications
- Installing and Viewing WebModules
- Solving Problems
- Where to Find More Information
- Glossary
- Index
26 Chapter 3 Managing Websites
Changing the Access Port for a Website
By default, the server uses port 80 for connections to websites on your server. You may
need to change the port used for an individual website, for instance, if you want to set
up a streaming server on port 80. Make sure that the number you choose does not
conflict with ports already being used on the server (for FTP, Apple File Service, SMTP,
and others). If you change the port number for a website you must change all URLs
that point to the web server to include the new port number you choose.
To set the port for a website:
1 In Server Admin, click Web in the list for the server you want.
2 Click Settings in the button bar.
3 In the Sites pane, double-click the site in the list.
4 In the General pane, type the port number in the Port field.
5 Click Save.
Web service restarts.
Improving Performance of Static Websites
(Performance Cache)
If your websites contain static HTML files, and you expect high usage of the pages, you
can enable the performance cache to improve server performance. The performance
cache is enabled by default.
You should disable the performance cache if:
• You do not anticipate heavy usage of your website.
• Most of the pages on your website are generated dynamically.
Understanding the Effect of Using a Web Service
Performance Cache
Web service's performance cache is enabled by default and significantly improves
performance for most websites. Sites that benefit most from the performance cache
contain mostly static content and can fit entirely in RAM. Website content is cached in
system RAM and is accessed very quickly in response to client requests.
Enabling the performance cache does not always improve performance. For example,
when the amount of static web content exceeds the physical RAM of your server, using
a performance cache increases memory swapping, which degrades performance.
Also note that when your server is running other services that compete for physical
RAM, such as AFP, the web performance cache may be less effective or may impact the
performance of those other services.
LL2350.book Page 26 Friday, August 22, 2003 2:32 PM