Mac OS X Server Web Technologies Administration For Version 10.
K Apple Computer, Inc. © 2005 Apple Computer, Inc. All rights reserved. The owner or authorized user of a valid copy of Mac OS X Server software may reproduce this publication for the purpose of learning to use such software. No part of this publication may be reproduced or transmitted for commercial purposes, such as selling copies of this publication or for providing paid-for support services. Every effort has been made to ensure that the information in this manual is accurate. Apple Computer, Inc.
1 Contents Preface 7 7 7 8 8 9 10 11 12 About This Guide What’s New in Version 10.
Chapter 3 4 25 26 26 26 27 27 28 29 29 29 30 30 30 31 31 31 31 32 Managing Weblogs (Blogs) Managing Connections Setting Simultaneous Connections for the Web Server Setting Persistent Connections for the Web Server Setting a Connection Timeout Interval Specifying Who Has Access to Web Service Setting Up Proxy Caching Blocking Websites From Your Web Server Cache Using Secure Sockets Layer (SSL) About SSL Using WebDAV Using Tomcat Using WebObjects Using JBoss Viewing Web Service Status Web Service Overview
0 50 52 52 52 53 53 54 54 Setting Server Responses to MIME Types and Content Handlers Enabling SSL Using a Passphrase With SSL Certificates Setting Up the SSL Log for a Website Enabling PHP User Content on Websites Web Service Configuration Default Content Accessing Web Content Chapter 4 57 57 57 58 58 59 59 WebMail WebMail Basics WebMail Users WebMail and Your Mail Server WebMail Protocols Enabling WebMail Configuring WebMail Chapter 5 61 61 61 62 62 62 62 63 63 64 64 65 66 67 68 68 69 69 Working W
72 72 72 72 72 73 73 mod_hfs_apple mod_digest_apple mod_bonjour Open Source Modules Tomcat PHP: Hypertext Preprocessor mod_perl Chapter 7 75 75 76 76 76 Solving Problems Users Can’t Connect to a Website on Your Server A Web Module Is Not Working as Expected A CGI Will Not Run The Server Is Not Working Correctly or Performance Is Slow Glossary 77 Index 81 Contents
Preface About This Guide This guide tells you how to set up and manage a web server, websites, and use open source web technologies. What’s New in Version 10.4 • Weblog service. Mac OS X Server provides a multiuser weblog server that complies with the RSS and Atom XML standards. Weblog service supports Open Directory authentication. For additional safety, users can access Weblog service using a website that’s SSL-enabled.
• Chapter 5, “Working With WebObjects and Web-Related Open Source Applications,” provides information and instructions related to WebObjects and open source components Apache, JBoss, Tomcat, and MySQL. • Chapter 6, “Installing and Viewing Web Modules,” describes the modules included in Mac OS X Server and explains how to install, enable, and view modules. • Chapter 7, “Solving Problems,” helps you address issues with web technologies and websites.
To see the latest server help topics, make sure the server or administrator computer is connected to the Internet while you’re using Help Viewer. Help Viewer automatically retrieves and caches the latest server help topics from the Internet. When not connected to the Internet, Help Viewer displays cached help topics.
This guide ... tells you how to: Mac OS X Server Windows Services Administration for Version 10.4 or Later Set up and manage services including PDC, BDC, file, and print for Windows computer users. Mac OS X Server Migrating from Windows NT to Version 10.4 or Later Move accounts, shared folders, and services from Windows NT servers to Mac OS X Server. Mac OS X Server Java Application Server Administration For Version 10.4 or Later Configure and administer a JBoss application server on Mac OS X Server.
Getting Additional Information For more information, consult these resources: Read Me documents—important updates and special information. Look for them on the server discs. Mac OS X Server website—gateway to extensive product and technology information. www.apple.com/macosx/server/ AppleCare Service & Support website—access to hundreds of articles from Apple’s support organization. www.apple.
If You’re an Experienced Server Administrator If you’re already familiar with network administration and you’ve used, Linux, UNIX, or a similar operating system, you may find these additional references useful. • Read Me documents—important updates and special information. Look for them on the server discs. • Apple Service & Support website—access to hundreds of articles from Apple’s support organization. www.apple.
1 Web Technologies Overview 1 Become familiar with web technologies and understand the major components before setting up your services and sites. Web Technologies Overview Web technologies in Mac OS X Server offer an integrated Internet server solution. Web technologies—also called web service in this guide—are easy to set up and manage, so you don’t need to be an experienced web administrator to set up multiple websites and configure and monitor your web server.
Since web service in Mac OS X Server is based on Apache, you can add advanced features with plug-in modules. Apache modules allow you to add support for Simple Object Access Protocol (SOAP), Java, and CGI languages such as Python. Key Web Components Web technologies in Mac OS X Server consist of several key components, which provide a flexible and scalable server environment. Apache Web Server Apache is an open source HTTP web server that administrators can configure with the Server Admin application.
SSL Support Web service includes support for Secure Sockets Layer (SSL), a protocol that encrypts information being transferred between the client and server. SSL works in conjunction with a digital certificate that provides a certified identity for the server by establishing a secure, encrypted exchange of information. Dynamic Content With Server Side Includes (SSI) Server side includes provide a method for using the same content on multiple pages in a site.
For more information about Apache modules, see the Apache Software Foundation website at http://www.apache.org. Providing Secure Transactions If you want to provide secure transactions on your server, you should set up Secure Sockets Layer (SSL) protection. SSL lets you send encrypted, authenticated information across the Internet. If you want to allow credit card transactions through your website, for example, you can use SSL to protect the information that’s passed to and from your site.
Understanding WebDAV If you use WebDAV to provide live authoring on your website, you should create realms and set access privileges for users. Each site you host can be divided into a number of realms, each with its own set of users and groups that have either browsing or authoring privileges. Defining Realms When you define a realm, which is typically a folder (or directory), the access privileges you set for the realm apply to all the contents of that directory.
Understanding Multipurpose Internet Mail Extension Multipurpose Internet Mail Extension (MIME) is an Internet standard for specifying what happens when a web browser requests a file with certain characteristics. You can choose the response you want the web server to make based on the file’s suffix. Your choices will depend partly on what modules you have installed on your web server. Each combination of a file suffix and its associated response is called a MIME type mapping.
Actions are handled differently. If you’ve mapped an action to a suffix, your server runs a program or script, and the result is served to the requesting browser. For example, if a browser requests a file with the suffix “cgi,” and its associated response is the action cgi-script, your server runs the script and returns the resulting data to the requesting browser.
Chapter 1 Web Technologies Overview
2 Managing Web Technologies 2 Use Server Admin to set up web technologies initially and to manage web settings and components. If you are familiar with web servers and their content, you can use these summary steps to get your web server started. If you’d like more detailed instructions for these tasks, see the similar topics in Chapter 3, “Managing Websites,” on page 33. Setting Up Your Web Server for the First Time Setting up your web server involves these procedures.
Step 3: Assign privileges for your website The Apache processes that serve webpages must have read access to the files, and read/execute access to the folders. (In the case of folders, execute access means the ability to read the names of files and folders contained in that particular folder.) Those Apache processes run as user www—a special user created specifically for Apache when Mac OS X Server is installed. The user www is a member of the group www.
Important: Always use Server Admin to start and stop the web server. You can start the web server from the command line, but Server Admin won’t show the change in status for several seconds. Server Admin is the preferred method to start and stop the web server and modify web server settings.
Starting Web Service Automatically Web service is set to start automatically (if it was running at shutdown) when the server starts up. This will ensure that your websites are available if there’s been a power failure or the server shuts down for any reason. When you start web service in the Server Admin toolbar, the service starts automatically each time the server restarts. If you turn off web service and then restart the server, you must turn web service on again.
4 In the new sheet that appears, do one of the following: For a new MIME type, type each part of the name (separated by a slash), select the suffix and type its name, use the Add button to add any suffixes you want, then click OK. For a new content handler, type a name for the handler, select the suffix and type its name, use the Add button to add any suffixes you want, then click OK.
Managing Connections You can limit the period of time that users are connected to the server. In addition, you can specify the number of connections to websites on the server at any one time. Setting Simultaneous Connections for the Web Server You can specify the number of simultaneous connections to your web server. When the maximum number of connections is reached, new requests receive a message that the server is busy. Simultaneous connections are concurrent HTTP client connections.
To set the number of persistent connections: 1 In Server Admin, click Web in the list for the server you want. 2 Click Settings in the button bar. 3 In the General pane, click Allow Persistent Connections if it is not checked. 4 Enter a number in the “Maximum persistent connections” field. The range for maximum persistent connections is 1 to 2048. 5 Click Save. Web service restarts when you save the changes. Note: The Apache documentation refers to persistent connects as “Keep-Alive.
Setting Up Proxy Caching A proxy lets users check a local server for frequently used files. You can use a proxy to speed up response times and reduce network traffic. The proxy stores recently accessed files in a cache on your web server. Browsers on your network check the cache before retrieving files from more distant servers. To take advantage of this feature, client computers must specify your web server as their proxy server in their browser preferences.
Blocking Websites From Your Web Server Cache If your web server is set up to act as a proxy, you can prevent the server from caching objectionable websites. Important: To take advantage of this feature, client computers must specify your web server as their proxy server in their browser preferences. You can import a list of websites by dragging it to list of sites. The list must be a text file with the host names separated by commas or tabs (also known as csv and tsv strings).
When a browser initiates a connection to an SSL-protected server, it connects to a specific port (443) and sends a message that describes the encryption ciphers it recognizes. The server responds with its strongest cipher, and the browser and server then continue exchanging messages until the server determines the strongest cipher both it and the browser recognize. Then the server sends its certificate (the Apache web server uses an ISO X.
Using JBoss JBoss is a widely used full-featured Java application server. It provides a full Java 2 Platform, Enterprise Edition (J2EE) technology stack with features such as: • An Enterprise Java Bean (EJB) container • Java Management Extensions (JMX) • Java Connector Architecture (JCA) You can set JBoss to start automatically whenever the server starts up. This ensures that the JBoss module starts up after a power failure or after the server shuts down for any reason.
Viewing and Searching Logs of Web Service Activity Web service in Mac OS X Server uses the standard Apache log format, so you can also use any third-party log analysis tool to interpret the log data. To view the log files: 1 In Server Admin, click Web in the list for the server you want. 2 Click Logs in the button bar. 3 Select the log you want to view in the list.
Managing Websites 3 3 Use the Server Admin application to set up and manage the essential components of web service. You administer websites on your server with Server Admin, an application that allows you to establish settings, specify folders and paths, enable a variety of options, and view the status of sites. Using Server Admin to Manage Websites The Sites pane in Server Admin lists your websites and provides some basic information about each site.
2 Replace the index.html file with the main page for your website. Make sure the name of your main page matches the default document name you set in the General pane of the site’s Settings window. See“Setting the Default Page for a Website” on page 36 for details. 3 Copy files you want to be available on your website to the Documents folder. Enabling a Website on a Server Before you can enable a website, you must create the content for the site and set up your site folders.
Virtual hosts are multiple sites on the same server. These sites can be named-based (such as www.example.com) or use IP addresses (such as 10.201.42.73). You can use the Server Admin application to manage both named-based, and IP-based virtual hosts. A multihomed site is a site that has more than one connection to the public Internet. Multihoming is typically done to improve reliability and performance.
Setting Up a Web Folder for a Site A site’s default web folder is used as the root for the site (called DocumentRoot in Apache). In other words, the default folder is the top level of the directory structure for the site. To change the default web folder for a site hosted on your server: 1 Log in to the server you want to administer. You need access to the file system on the server. 2 Drag the contents of your previous web folder to your new web folder.
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).
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. Note: If you turn on SSL, the performance cache is automatically turned off.
3 In the Sites pane, double-click the site in the list. 4 In the Options pane, click Performance Cache to change its state. 5 Click Save. You can also improve server performance by disabling the access log. Interaction Between the Performance Cache and Apache The Apache web server uses port 16080 when the performance cache is enabled. Blocking this port could interfere with web service.
If you are administering a remote server, file service must be running on the remote server to use the Browse button. 7 Choose a log format from the Format pop-up menu. 8 Edit the format string, if necessary. Note: The Help button next to the format string opens the Apache documentation web page (http://httpd.apache.org/docs/mod/mod_log_config.html#formats), which explains the parameters for format strings. 9 Enter archive, location, and level choices for the error log as desired. 10 Click Save.
When the performance cache is enabled (default) the “%h” item will extract the local machine’s IP address. To extract the remote client’s IP address, the log format string needs to be modified as follows: %{PC-Remote-Addr}i %l %u %t "%r" %>s %b When you use the Server Admin application to enable and disable web performance cache for each site (virtual host), the CustomLog directive in httpd.
Step 2: Import your web content Import your web content into the Spotlight MetaData store. The /Library/WebServer/ Documents folder is not normally monitored by the MetaData Import processes, so you need to import the data manually, both initially and whenever you want any changes to be reflected. It’s a good practice to create different folders to hold the content of your virtual hosts. You need to manually import and update those as well. You use the mdimport command-line too to import the data.
To make sure a website is working properly: 1 Open a web browser and type the web address of your server. You can use either the IP address or the DNS name of the server. If you’ve enabled SSL, be sure to use “https” in the URL instead of “http.” 2 Type the port number, if you are not using the default port. 3 If you’ve restricted access to specific users, enter a valid user name and password.
9 Select Can Browse and Can Author for each user and group as desired. Note: When users or members of a group you’ve added to the realm connect to the site, they must supply their user name and password. 10 Click Save. Use the Realms pane to delete a user or group by selecting the name and clicking the Delete (-) button. Enabling WebDAV on Websites Web-based Distributed Authoring and Versioning (WebDAV) allows you or your users to make changes to websites while the sites are running.
Using WebDAV to Share Files You can use WebDAV to allow authorized users to connect to a website on the server and to share files on that site. The steps below provide a brief example of setting up and using shared files using WebDAV. • Turn on WebDAV for the site in Server Admin. See “Enabling WebDAV on Websites” on page 44 for details. • Set up Realms for the site in Server Admin to control access to the site. See “Setting Access for Websites” on page 43 for details.
If you want to use WebDAV, you need to enable it in Server Admin and manually change the web content files’ or folders’ ownership to user and group www. If you are using WebDAV and you want to make changes to web content files or folders while logged in as an administrator, you need to change the web content file and folder permissions to admin, make your edits, and then restore the file and folder permissions to www.
Sample Aliases and Redirects The examples below show aliases and redirects. • Alias: For a host named “example.com” you might want to provide a server alias named “www.example.com.” • Redirect: Pattern: /images/boats.jpg Path: http://www.apple.com In this example, if the user enters the URL /images/boats.jpg and the site has a folder “images” containing the file “boats.jpg,” the user’s browser will be redirected to www.apple.com.
4 Type the path for the alias or redirect and click OK. This is the path in the file system or the redirect that gets sent back to the querier. 5 Click Save. Sample Aliases and Redirects The examples below show aliases and redirects. • Alias: pattern: /images path: /Volumes/Data/imgs If you have made a file system change but you don’t want to have to change all of the image URLs in your HTML files, this will translate http://www.example.com/ images/boat.jpg to grab the file from /Volumes/Data/boat.jpg.
Enabling a Common Gateway Interface (CGI) Script Common Gateway Interface (CGI) scripts (or programs) send information back and forth between your website and applications that provide different services for the site. If a CGI is to be used by only one site, install the CGI in the Documents folder for the site. The CGI name must end with the suffix “.cgi.” If a CGI is to be used by all sites on the server, install it in the /Library/WebServer/CGIExecutables folder.
• The port being used for the site Double-clicking a site in the Sites pane opens the site details window, where you can view or change the settings for the site. Setting Server Responses to MIME Types and Content Handlers Multipurpose Internet Mail Extension (MIME) is an Internet standard for specifying what happens when a web browser requests a file with certain characteristics. Content handlers are similar and also use suffixes to determine how a file is handled.
To set up SSL 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 Security pane, select Enable Secure Sockets Layer (SSL). When you turn on SSL, a message notes that the port is changed to 443. 5 Type the location of the SSL log file in the SSL Log File field. You can also click the Browse button to locate the folder you want to use.
Using a Passphrase With SSL Certificates If you manage SSL certificates using the Server Admin application, and you use a passphrase for your certificates, Server Admin ensures that the passphrase is stored in the system keychain. When a website is configured to use the certificate and that web server is started, the getsslpassphrase(8) utility extracts the passphrase from the system keychain and passes it to the web server, as long as the certificate name matches the virtual host name.
To enable PHP: 1 In Server Admin, click Web for the server you want. 2 Click Settings in the button bar. 3 In the Modules pane, scroll to php4_module in the module list and click Enabled for the module, if necessary. 4 Click Save. User Content on Websites Mac OS X client has a Personal Web Sharing feature, where a user may place content in the Sites folder of his or her home directory and have it visible on the web.
Default Content The default content for the user’s Sites folder is an index.html file along with a few images. It is important to note that this index.html file has text that describes the Personal Web Sharing feature of Mac OS X client. The user should replace that index.html file with one suited to the content of his or her Sites folder. Accessing Web Content Once the home directory is created, the content of the Sites folder within the user’s home directory is visible whenever web service is running.
http://example.com/Protected/sECreT But they could bypass it by using something like the following: http://example.com/PrOtECted http://example.com/PrOtECted/secret http://example.com/PrOtECted/sECreT Fortunately, mod_hfs_apple prevents those types of efforts to bypass the security realm, and this module is enabled by default. Note: mod_hfs_apple operates on folders; it is NOT intended to prevent access to individual files. A file named “secret” can be accessed as “seCREt”.
Chapter 3 Managing Websites
4 WebMail 4 Enable WebMail for the websites on your server to provide access to basic email operations by means of a web connection. WebMail adds basic email functions to your website. If your web service hosts more than one website, WebMail can provide access to mail service on any or all of the sites. The mail service looks the same on all sites. WebMail Basics The WebMail software is included in Mac OS X Server, but is disabled by default. The WebMail software is based on SquirrelMail (version 1.4.
Users log in to WebMail with the name and password they use for logging in to regular mail service. WebMail does not provide its own authentication. For more information on mail service users, see the mail service administration guide. When users log in to WebMail, their passwords are sent over the Internet in clear text (not encrypted) unless the website is configured to use SSL. For instructions on configuring SSL, see “Enabling SSL” on page 50.
Enabling WebMail You can enable WebMail for the website (or sites) hosted by your web server. Changes take effect when you restart web service. To enable WebMail for a site: 1 Make sure your mail service is started and configured to provide IMAP and SMTP service. 2 Make sure IMAP mail service is enabled in the user accounts of the users you want to have WebMail access. For details on mail settings in user accounts, see the user management guide.
You can configure these and other settings—such as which mail server provides mail service for WebMail—by running an interactive Perl script in a Terminal window, with root privileges. The script operates by reading original values from the config.php file and writing new values back to config.php. Important: If you use the interactive configuration script to change any SquirrelMail settings, you must also use the script to enter your server’s domain name.
5 Working With WebObjects and Web-Related Open Source Applications 5 Become familiar with WebObjects and the open source applications Mac OS X Server uses to administer and deliver web services. The application server component of Mac OS X Server offers versatile tools that allow you to extend your web server in a variety of ways. The Apple web development tool WebObjects is represented in the application server. In addition, several open source applications provide essential features of web service.
serveradmin start webobjects serveradmin stop webobjects Changing the WebObjects Configuration You use Server Admin to change the WebObjects configuration. 1 In Server Admin click WebObjects in the list for the server you want. 2 Click Settings in the button bar. 3 Specify the wotaskd (WebObjects Task Daemon) port or the Monitor port, as desired, or turn Monitor on. 4 Click Save. Opening the Java Monitor Application The Java Monitor helps you configure WebObjects applications.
Note: All files in /etc/httpd/sites/ are read and processed by Apache when it does a hard or soft (graceful) restart. Each time you save changes, the server does a graceful restart. If you edit a file using a text editor that creates a temporary or backup copy, the server restart may fail because two files with almost identical names are present. To avoid this problem, delete temporary or backup files created by editing files in this folder.
• The apachectl script does not increase the soft process limit beyond the default of 100. Server Admin raises this limit when it starts Apache. If your web server receives a lot of traffic and relies on CGI scripts, web service may fail to run when it reaches the soft process limit. • The apachectl script does not start Apache automatically when the server restarts.
After you enable Tomcat using the Application Server section of Server Admin, you can validate the preinstalled Apache Axis by browsing the following: http://example.com:9006/axis/ Replace “example.com” in the URL above with your host name. Note the nonstandard Tomcat port. The first time you exercise the preinstalled Axis by browsing http://example.
JBoss JBoss (version 3.2.3) is an open source application server designed for J2EE applications; it runs on Java 1.4.2. JBoss is a widely used, full-featured Java application server.
4 Click Start Service or Stop Service. To start or stop JBoss using Terminal: 1 Open the Terminal application. 2 Type the following commands. cd /Library/JBoss/3.2/bin ./run.sh JBoss is preconfigured to use a local configuration. With JBoss turned on, you can use the management tool to configure your server.
Tomcat Tomcat is the open source servlet container that is used as the official Reference Implementation for the Java Servlet and JavaServer Pages technologies. The Java Servlet and JavaServer Pages specifications are developed by Sun under the Java Community Process. The current production series is the Tomcat 4.1.x series and it implements Java Servlet 2.3 and JavaServer Pages 1.2 specifications. More information is available from the following sources: • For Java Servlet specifications, see java.sun.
To verify that Tomcat is running, use a browser to access port 9006 of your website by entering the URL for your site followed by :9006. If Tomcat is running, this URL will display the Tomcat home page. MySQL MySQL provides a relational database management solution for your web server. With this open source software, you can link data in different tables or databases and provide the information on your website. The MySQL Manager application simplifies setting up the MySQL database on Mac OS X Server.
Note that the MySQL Manager application works only with the preinstalled version of MySQL; it does not work with MySQL installed elsewhere. The paths to the various preinstalled components of MySQL are stored in the following plist file: /Applications/Server/MySQL Manager.app/Contents/Resources/tool_strings. If You Are Updating from Mac OS X Server 10.2 or Earlier and Use MySQL Previous versions of the server contained MySQL 3.23.x; the version now installed is 4.1, which is the latest production version.
6 Installing and Viewing Web Modules 6 Become familiar with the modules that provide key features and controls for web service. The Apache web server includes a series of modules that control the server’s operation. In addition, Mac OS X Server provides some modules with specialized functions for the Macintosh. Apache Modules Modules “plug in” to the Apache web server software and add functionality to your website.
mod_spotlight_apple This module lets Apache perform relevance-ranked searches of the website using Spotlight. Once you index your site, you can provide a search field for users to search your website. Clients must add .spotlight to your website’s URL to access a page that allows them to search your site. For example, http://www.example.com/.spotlight. mod_auth_apple This module allows a website to authenticate users by looking for them in directory service domains within the server’s search policy.
PHP: Hypertext Preprocessor PHP lets you handle dynamic web content by using a server side HTML-embedded scripting language resembling C. Web developers embed PHP code within HTML code, allowing programmers to integrate dynamic logic directly into an HTML script rather than write a program that generates HTML. PHP provides CGI capability and supports a wide range of databases. Unlike client-side JavaScript, PHP code is executed on the server. PHP is also used to implement WebMail on Mac OS X Server.
Chapter 6 Installing and Viewing Web Modules
7 Solving Problems 7 If you experience a problem with web service or one of its components, check the tips and strategies in this chapter. From time to time you may encounter a problem when setting up or managing web services. Some of the situations that may cause a problem for administering web service or for client connections are outlined here.
A Web Module Is Not Working as Expected Try several strategies to uncover the problem. • Check the error log in Server Admin for information about why the module might not be working correctly. • If the module came with your web server, check the Apache documentation for that module and make sure the module is intended to work the way you expected.
Glossary Glossary Apache An open source HTTP server integrated into Mac OS X Server. You can find detailed information about Apache at www.apache.org. application server Software that runs and manages other applications, usually web applications, that are accessed using a web browser. The managed applications reside on the same computer where the application server runs. blog See weblog. Blojsom The open-source project on which Weblog service is based.
IP Internet Protocol. Also known as IPv4. A method used with Transmission Control Protocol (TCP) to send data between computers over a local network or the Internet. IP delivers packets of data, while TCP keeps track of data packets. IP address A unique numeric address that identifies a computer on the Internet. JavaScript A scripting language used to add interactivity to webpages.
proxy server A server that sits between a client application, such as a web browser, and a real server. The proxy server intercepts all requests to the real server to see if it can fulfill the requests itself. If not, it forwards the request to the real server. realm See WebDAV realm, Kerberos realm. SSL Secure Sockets Layer. An Internet protocol that allows you to send encrypted, authenticated information across the Internet. More recent versions of SSL are known as TLS (Transport Level Security).
Glossary
Index Index A access for websites setting 43 access privileges setting for WebDAV 17 websites 17, 22 aliases 46 Apache module 14, 16, 70, 71 Apache modules 71 Apache web server 14, 71 configuration 15 Apache website 12 C cache. See proxy cache CGI (Common Gateway Interface) 14 CGI programs problems with 76 CGI scripts enabling 49 installing 49 solving problems 76 D documentation 9 Documents folder 21 F folders Documents folder 21 H help 8 I indexes creating 41 Internet servers.
P Perl mod_perl 73 PHP (PHP Hypertext Preprocessor) 73 Apache module 73 enabling 52 PHP Hypertext Preprocessor (PHP) See PHP (PHP Hypertext Preprocessor) proxy 28 blocking websites with 29 proxy cache enabling 28 proxy server 29 R realms using for website access 43 realms, WebDAV 17 redirect 46 S scripts See CGI scripts searching Spotlight 41 security WebDAV 17 Server Admin 33 configuring web server 15 modifying MIME type mappings 24, 25 starting or stopping web service 23 starting Tomcat 31 viewing web s
secure transactions 16, 50 settings for 23 setting up 21–23 setting up websites 16 solving problems 75 SSL, enabling 29 starting 23 stopping 23 Tomcat 30 WebDAV 30 WebMail, managing 59–60 website privileges 22 websites 33–53 access privileges 17 assigning privileges 22 connecting to 23 connection problems 75 default page 21, 36 Index directory listing 41 documents Folder 33 enabling 34 hosting 16, 22 improving performance 37 information about 33 logs 39 MIME, configuring 50 monitoring 49 multiple 34 setti
