KeepAliveTimeout directive
Syntax: KeepAliveTimeout seconds
Default: KeepAliveTimeout 15
Context: server config
Status: Core
Compatibility: KeepAliveTimeout is only available in Apache 1.1 and later.
The number of seconds Apache will wait for a subsequent request before closing the connection. Once a request has been received, the timeout value specified by the Timeout directive applies.
--------------------------------------------------------------------------------
<Limit> directive
Syntax: <Limit method method ... > ... </Limit>
Context: any
Status: core
Access controls are normally effective for all access methods, and this is the usual desired behaviour. In the general case, access control directives should not be placed within a <limit> section.
The purpose of the <Limit> directive is to restrict the effect of the access controls to the nominated HTTP methods. For all other methods, the access restrictions that are enclosed in the <Limit> bracket will have no effect. The following example applies the access control only to the methods POST, PUT, and DELETE, leaving all other methods unprotected:
<Limit POST PUT DELETE>
require valid-user
</Limit>
The method names listed can be one or more of: GET, POST, PUT, DELETE, CONNECT, OPTIONS, TRACE, PATCH, PROPFIND, PROPPATCH, MKCOL, COPY, MOVE, LOCK, and UNLOCK. The method name is case-sensitive. If GET is used it will also restrict HEAD requests.
--------------------------------------------------------------------------------
<LimitExcept> directive
Syntax: <LimitExcept method method ... > ... </LimitExcept>
Context: any
Status: core
Compatibility: Available in Apache 1.3.5 and later
<LimitExcept> and </LimitExcept> are used to enclose a group of access control directives which will then apply to any HTTP access method not listed in the arguments; i.e., it is the opposite of a <Limit> section and can be used to control both standard and nonstandard/unrecognized methods. See the documentation for <Limit> for more details.
AuthName directive
Syntax: AuthName auth-domain
Context: directory, .htaccess
Override: AuthConfig
Status: core
This directive sets the name of the authorization realm for a directory. This realm is given to the client so that the user knows which username and password to send. AuthName takes a single argument; if the realm name contains spaces, it must be enclosed in quotation marks. It must be accompanied by AuthType and require directives, and directives such as AuthUserFile and AuthGroupFile to work.
--------------------------------------------------------------------------------
AuthType directive
Syntax: AuthType type
Context: directory, .htaccess
Override: AuthConfig
Status: core
This directive selects the type of user authentication for a directory. Only Basic and Digest are currently implemented. It must be accompanied by AuthName and require directives, and directives such as AuthUserFile and AuthGroupFile to work.
--------------------------------------------------------------------------------
BindAddress directive
Syntax: BindAddress saddr
Default: BindAddress *
Context: server config
Status: core
A Unix® http server can either listen for connections to every IP address of the server machine, or just one IP address of the server machine. Saddr can be
*
An IP address
A fully-qualified Internet domain name
If the value is *, then the server will listen for connections on every IP address, otherwise it will only listen on the IP address specified.
Only one BindAddress directive can be used. For more control over which address and ports Apache listens to, use the Listen directive instead of BindAddress.
BindAddress can be used as an alternative method for supporting virtual hosts using multiple independent servers, instead of using <VirtualHost> sections.
See Also: DNS Issues
See Also: Setting which addresses and ports Apache uses
如今网络技术如日中天，才见CGI(Common Gateway Interface)又出ASP(Active Serve Page)，接着杀出PHP(见后注)，真是令人手忙脚乱目不暇接。这些新软件的出现，不仅给我们带来了全新的感受，同时也给我等配置较低的机器如何玩这些软件带来了问题，本文就我自己的体会，阐述在较低机器配置下如何安装PHP4.0软件。
本人的“爱鸡”配置是：联想天琴909的改造产品:MMX166换成K6Ⅱ－400,内存仍为32兆字节,主板核心电压跳到2.2V……
软件只需要Windows 98＋PWS(Personal Web Server)，NT、LINUX、Win 2000一律不用装。安装过程如下：
1、您可以从Windows 98(正式版或OEM版)的安装盘的add－onspwssetup.exe中安装PWS，选典型安装或定制安装,使用缺省安装目录C:Inetpubwwwroot(完成单机改造成服务器的宏伟工程)。
2、软件下载：http://www.php.net/distributions/php－4.0.0－Win32.zip或http://soft.km169.net/soft/wybc/php-4.0.0-win32.zip!
3、用解压缩工具把php－4.0.0－Win32.zip解压到PHP安装目录，如C:php（可不要说你没有WinZip呀）!
4、将PHP安装目录下的php.ini－dist文件拷贝到C:WINDOWS目录，并将C:WINDOWSphp.ini－dist改名为C:WINDOWSphp.ini；
5、将PHP安装目录下的Msvcrt.dll和php4ts.dll拷贝到C:WINDOWSSystem目录，如果C:WINDOWSSystem目录下已经存在这些文件，请不要覆盖(事先查找一下有无Msvcrt.dll)；
6、修改C:WINDOWSphp.ini：
1) 将Extension_dir设置为PHP安装目录，如：extension_dir =C:php（在php.ini中左看右看，即可找到）；
2) 配置要加载的动态链接库(DLL)，注意一定要保证只能加载PHP安装目录下存在的动态链接库，如有不同的动态链接库名称,请改成与该版本自带这些动态链接库：php_calendar.dll、php_imap.dll、php_ldap.dll相一致，因此动态链接库的配置栏如下(一定要将;去掉)：
Windows Extensions
extension=php_calendar.dll
extension=php_imap.dll
在RedHat6.2上安装apache1.3.12+gd1.8.3+php4.04+tomcat+sybase11.9.2+oracle8.1.6+mysql全攻略 <br>
<br>
看了网上众多网友对php、jsp、sybase、oracle、apache等方面的安装经验，发现有很多都是重复而且不够全面，根据本人对以上各种东东长期总结和参考相关文档以及各位网友的文章，并经自己亲自实践，现将在RedHat6.2下apache1.3.12+gd1.8.3+php4.04+tomcat+sybase11.9.2+oracle8.1.6+mysql3.22.27的安装配置全部奉献给大家，希望能对大家有所帮助； <br>
<br>
运行环境：PⅢ550+256M+20G+530TX Lan+sis6326 8M+RedHat Linux6.2 <br>
安装规划：sybase安装在/sybase目录 <br>
oracle安装在/home/oracle目录 <br>
gd安装在/usr/local目录 <br>
apache安装在/www目录 <br>
tomcat安装在/usr/local/jakarta-tomcat目录 <br>
jdk安装在/usr/local/jdk122目录 <br>
<br>
一、资料准备 <br>
1、apache_1312.tar.gz <br>
2、php-404.tar.gz <br>
3、jakarta-tomcat.tar.gz <br>
4、sybase11.9.2包: <br>
sybase-common-1192-1i386.rpm <br>
sybase-ase-1192-1i386.rpm <br>
sybase-monserver-1192-1i386.rpm <br>
sybase-openclient-1111-1i386.rpm <br>
sybase-sqlremote-602-1i386.rpm <br>
sybase-chinese-1192-1i386.rpm <br>
5、oracle8.1.6.tar <br>
6、mysql3.22.27包： <br>
mysql-3.22.27-1.i386.rpm <br>
mysql-devel-3.22.27-1.i386.rpm <br>
mysql-client-3.22.27-1.i386.rpm <br>
7、jdk1_2_2-linux-i386.tar.gz <br>
8、mod-jserv.so <br>
9、gd183.tar.gz <br>
<br>
二、环境配置 <br>
1、系统安装 <br>
安装linux系统时创建目录/www、/sybase和/home并分配给各自较大空间，用于存储数据库资料和网页文件； <br>
2、环境变量 <br>
配置运行oracle和tomcat以及java的java运行环境变量 <br>
用root用户登录系统 <br>
＃vi /etc/profile <br>
添加下列行 <br>
ORACLE_HOME=/home/oracle <br>
本文作者：原奥索网用户 herodong OICQ：6678705
/* 孤狼：原文实在太大了，36K多。我选择重要部分贴上，如果需要原文可以MAILTO：wolflx@263.net
我们的目标是安装一个允许我们托管多个网站的web服务器，其中一些是针对电子商务的安全解决方案，而大部分网站是通过连接一个数据库服务器并且提取其数据的脚本驱动的。
为了这个任务所需的工具是：
Apache－一个网站服务器
Mod_SSL－一个安全套接字层(SSL)的模块
OpenSSL－开放源代码工具箱(mod_ssl所需）
RSARef－仅对美国用户
MySQL－一个数据库服务器
PHP－一种脚本语言
“条条大路通罗马”……因此这只是很多能达到我们要求的配置之一。我选择这样的配置，是因为它是最简单和最快的一种。选择Mod_SSL/OpenSSL的原因是因为我有它的先前经验，是最快配置和最容易安装的一种。为了彼此方便地与Apache集成，我选择了PHP和MySQL。记住，Perl能做到你想要做任何工作，然而，PHP对任何想学习它地程序员来说简单并且容易。
希望你将在结束这个简单的指南后能成功地完成下列目标。
安装并设置MySQL数据库服务器
安装并设置具备SSL的Apache网站服务器
安装并配置服务器端脚本的PHP 4.0超文本预处理器
创造一些样本证书用于Apache SSL
本文假设你已经把下列软件安装在你的系统上了。
Perl (最好是ver 5+)
gzip或gunzip
gcc 和 GNU make
准备
Apache (Web服务器)-http://www.apache.org
Mod_SSL (安全服务器层)-http://www.modssl.org
OpenSSL (SSL工具箱)-http://www.openssl.org
PHP (脚本语言)-http://www.php.net
MySQL (SQL数据库服务器 )-http://www.mysql.com
下载所有(tar文件)源代码到一个临时目录下。保证你把他们放在有很多空间的地方……你应该以root身份下载他们以避免权限问题。
我们的计划
我们的计划是首先安装MySQL服务器并保证它工作，然后我们将安装PHP和Mod_SSL，最后我们将安装Apache网站服务器。在我们安装了Apache以后，我们可以测试PHP和Mod_SSL支持是否起作用了。
MySQL源代码安装(UNIX)
你必须用来执行安装MySQL源代码分发的基本命令是(自一个没解开“tar”文件)：
通过使用su成为 root用户。
$su
直接进入你有tar文件的目录。（使用一个临时目录。这里使用 /tmp/download/ ）