| Up to higher level directory | |||
| Name | Date | Size | |
|---|---|---|---|
| ABOUT_APACHE | 24-Nov-2004 | 14.4K | |
| cgi-bin/ | 10-Jan-2008 | ||
| conf/ | 10-Jan-2008 | ||
| config.layout | 24-Nov-2004 | 9.2K | |
| configure | 12-Jul-2006 | 53.3K | |
| htdocs/ | 10-Jan-2008 | ||
| icons/ | 10-Jan-2008 | ||
| INSTALL | 24-Nov-2004 | 27.3K | |
| LICENSE | 06-Dec-2004 | 19.9K | |
| logs/ | 10-Jan-2008 | ||
| Makefile.tmpl | 12-Jul-2006 | 24.9K | |
| NOTICE | 27-Jul-2006 | 815 | |
| NWGNUenvironment.inc | 31-Oct-2005 | 3.9K | |
| NWGNUhead.inc | 24-Nov-2004 | 1.9K | |
| NWGNUmakefile | 10-Oct-2005 | 1.1K | |
| NWGNUtail.inc | 24-Apr-2007 | 7.9K | |
| README | 24-Nov-2004 | 2K | |
| README-WIN.TXT | 24-Nov-2004 | 4K | |
| README.configure | 24-Nov-2004 | 10.9K | |
| src/ | 10-Jan-2008 | ||
| WARNING-WIN.TXT | 24-Nov-2004 | 1.3K | |
README
1 2 Apache 3 Version 1.3 (and up) 4 5 What is it? 6 ----------- 7 8 Apache is an HTTP server designed as a plug-in replacement for 9 the NCSA server version 1.3 (or 1.4). It fixes numerous bugs in 10 the NCSA server and includes many frequently requested new 11 features, and has an API which allows it to be extended to meet 12 users' needs more easily. 13 14 The Latest Version 15 ------------------ 16 17 Details of the latest version can be found on the Apache HTTP 18 server project page under http://httpd.apache.org/. 19 20 Documentation 21 ------------- 22 23 The documentation available as of the date of this release is 24 also included, in HTML format, in the htdocs/manual/ directory. 25 For the most up-to-date documentation can be found on 26 http://httpd.apache.org/docs/. 27 28 Installation 29 ------------ 30 31 From Apache version 1.3 and up you have two possibilities to 32 build and install the Apache package: The old commonly known 33 but manual way from Apache 1.2 and below and the new 34 out-of-the-box way through the new Apache Autoconf-style 35 Interface (APACI). For detailed instructions see the file 36 INSTALL in this directory. 37 38 Licensing 39 --------- 40 41 Please see the file called LICENSE. 42 43 Acknowledgments 44 ---------------- 45 46 We wish to acknowledge the following copyrighted works that 47 make up portions of the Apache software: 48 49 Portions of this software were developed at the National Center 50 for Supercomputing Applications (NCSA) at the University of 51 Illinois at Urbana-Champaign. 52 53 This software contains code derived from the RSA Data Security 54 Inc. MD5 Message-Digest Algorithm, including various 55 modifications by Spyglass Inc., Carnegie Mellon University, and 56 Bell Communications Research, Inc (Bellcore). 57 58 This package contains a modified version of software written and 59 copyrighted by Henry Spencer. Please see the file called 60 src/regex/COPYRIGHT. 61 62 The NT port was started with code provided to the Apache Group 63 by Ambarish Malpani of ValiCert, Inc. (http://www.valicert.com/). 64 65
README-WIN.TXT
1 Apache 2 Version 1.3 (and up) 3 4 What is it? 5 ----------- 6 7 Apache is an HTTP server, originally designed for Unix systems. This 8 is the version of Apache for Microsoft Windows 2000, NT, 98, and 95 9 systems. Like the Unix version, it includes many frequently 10 requested new features, and has an API that allows it to be extended 11 to meet users' needs more easily. It also allows limited support for 12 ISAPI extensions. 13 14 15 The Latest Version 16 ------------------ 17 18 Details of the latest version can be found on the Apache HTTP 19 server project page under http://httpd.apache.org/. 20 21 Documentation 22 ------------- 23 24 The documentation available as of the date of this release is 25 also included, in HTML format, in the htdocs/manual/ directory. 26 For the most up-to-date documentation can be found on 27 http://httpd.apache.org/docs/. For Windows specific information, see 28 http://httpd.apache.org/docs/windows.html. 29 30 WARNING 31 ------- 32 33 Apache should never be used as a production server under any 34 consumer operating system such as Windows 95, 98, or ME (Millennium 35 Edition). Only Windows NT 4.0 or 2000 should be considered, and only 36 with appropriate NTFS file system and user security administration. 37 Apache runs on these consumer Windows environments only to 38 provide test, development or trusted intranet server platforms. 39 40 Apache on Win32 should be considered initial-release quality code. 41 It has not been subjected to the same stresses on its stability and 42 security that the Unix releases have enjoyed, so there is a greater 43 possibility of undiscovered vulnerabilities to stability or security 44 of the Win32 port. 45 46 Apache performs best, and is still most reliable on Unix platforms. 47 Over time the performance, reliability and security for the Apache 48 Win32 port has improved, and continues to improve. Folks doing 49 comparative reviews of webserver performance are still asked to 50 compare against Apache running on a Unix platform such as 51 Solaris, FreeBSD, or Linux. 52 53 The Win32 code for Apache 2.0 has been entirely revised and large 54 segments have been rewritten from scratch. Once the Apache 2.0 55 server is released, we strongly encourage all Win32 users to move to 56 that platform for increased stability and security. 57 58 Installation 59 ------------ 60 61 See the http://httpd.apache.org/docs/windows.html for details of how 62 to install, configure and run Apache. These documents are also 63 accessable from the "Documentation" program group listed within the 64 "Apache Web Server" Start Menu programs group created by the full 65 Apache Win32 program installer. 66 67 Known Problems 68 -------------- 69 70 To get information about the current set of known problems, see the 71 online bug reporting database at 72 73 http://www.apache.org/bug_report.html 74 75 Bugs which affect Apache on Windows and not Apache on Unix can be 76 found under the category "os-windows". 77 78 Do not report configuration problems to this database. Please first 79 research the problem you are experiencing on the newsgroup 80 news:comp.infosystems.www.servers.ms-windows and search the bugs 81 database before posting a bug report. 82 83 Licensing 84 --------- 85 86 Please see the file called LICENSE. 87 88 Acknowledgments 89 ---------------- 90 91 We wish to acknowledge the following copyrighted works that 92 make up portions of the Apache software: 93 94 Portions of this software were developed at the National Center 95 for Supercomputing Applications (NCSA) at the University of 96 Illinois at Urbana-Champaign. 97 98 This software contains code derived from the RSA Data Security 99 Inc. MD5 Message-Digest Algorithm, including various 100 modifications by Spyglass Inc., Carnegie Mellon University, and 101 Bell Communications Research, Inc (Bellcore). 102 103 This package contains software written and copyrighted by Henry 104 Spencer. Please see the file called src/regex/COPYRIGHT. 105 106 The NT port was started with code provided to the Apache Group 107 by Ambarish Malpani of ValiCert, Inc. (http://www.valicert.com/). 108 109 110
README.configure
1 2 APACHE CONFIGURATION 3 4 Apache 1.3 Autoconf-style Interface (APACI) 5 =========================================== 6 7 APACI is an Autoconf-style interface for the Unix side of the Apache 1.3 8 HTTP server source distribution. It is actually not GNU Autoconf-based, i.e. 9 the GNU Autoconf package itself is not used. Instead APACI just provides a 10 similar batch configuration interface and a corresponding out-of-the-box 11 build and installation procedure. 12 13 The basic goal is to provide the following commonly known and expected 14 procedure for out-of-the-box building and installing a package like Apache: 15 16 $ gunzip <apache_1.3.X.tar.gz | tar xvf - 17 $ ./configure --prefix=PREFIX [...] 18 $ make 19 $ make install 20 21 NOTE: PREFIX is not the string "PREFIX". Instead use the Unix 22 filesystem path under which Apache should be installed. For 23 instance use "/usr/local/apache" for PREFIX above. 24 25 After these steps Apache 1.3 is completely installed under PREFIX and 26 already initially configured, so you can immediately fire it up the first 27 time via 28 29 $ PREFIX/sbin/apachectl start 30 31 to get your first success event with the Apache HTTP server without having 32 to fiddle around with various options for a long time. On the other hand 33 APACI provides a lot of options to adjust the build and installation process 34 for flexibly customizing your Apache installation. So, APACI provides both: 35 Out-of-the-box building and installation for the impatient and powerful 36 custom configuration for the experts. 37 38 Detailed Description 39 ==================== 40 41 For a detailed description of all available APACI options please read the 42 file INSTALL or at least run the command 43 44 $ ./configure --help 45 46 for a compact one-page summary of the possibilities you have. 47 Alternatively, you can start from the following examples. 48 49 Examples 50 ======== 51 52 In the following typical or even interesting variants of the available 53 configuration steps are shown to give you an impression what APACI is good 54 for and what APACI can do for you to be able to install Apache without much 55 pain. 56 57 Standard installation 58 --------------------- 59 60 The standard installation is done via 61 62 $ ./configure --prefix=/path/to/apache 63 $ make 64 $ make install 65 66 This builds Apache 1.3 with the standard set of enabled modules 67 (automatically determined from src/Configuration.tmpl) with an Apache 1.2 68 conforming subdirectory layout under /path/to/apache. For using the GNU 69 style subdirectory layout additionally use the --with-layout=GNU option: 70 71 $ ./configure --with-layout=GNU --prefix=/path/to/apache 72 $ make 73 $ make install 74 75 If you are not sure which directory layout you want, you can use the 76 --show-layout option. It displays the directory layout which would be used 77 but immediately exits without configuring anything. Examples: 78 79 $ ./configure --show-layout 80 $ ./configure --prefix=/path/to/apache --show-layout 81 $ ./configure --with-layout=GNU --prefix=/path/to/apache --show-layout 82 83 Additionally if some of the shown paths still don't fit for your particular 84 situation, you can use the --bindir, --sbindir, --libexecdir, --mandir, 85 --sysconfdir, --datadir, --localstatedir, --runtimedir, --logfiledir and 86 --proxycachedir options to adjust the layout as required. Always check with 87 --show-layout the resulting directory layout which would be used for 88 installation. 89 90 suEXEC support 91 -------------- 92 93 The suEXEC feature of Apache provides a mechanism to run CGI and SSI 94 programs under the user and group id of the owner of the program. It is 95 neither installed nor configured per default for Apache 1.3, but APACI 96 supports it with additional options: 97 98 $ ./configure --prefix=/path/to/apache \ 99 --enable-suexec \ 100 --suexec-caller=www \ 101 --suexec-userdir=.www \ 102 --suexec-docroot=/path/to/root/dir \ 103 --suexec-logfile=/path/to/logdir/suexec_log \ 104 --suexec-uidmin=1000 \ 105 --suexec-gidmin=1000 \ 106 --suexec-safepath="/bin:/usr/bin" 107 $ make 108 $ make install 109 110 This automatically builds and installs Apache 1.3 with suEXEC support for 111 the caller uid "www" and the user's homedir subdirs ".www". The default 112 paths for --suexec-docroot is the value from the --datadir option with 113 the suffix "/htdocs" and the --logfiledir value with the suffix 114 "/suexec_log" for the --suexec-logfile option. The access paths for the 115 suexec program are automatically adjusted and the suexec program is 116 installed, so Apache can find it on startup. 117 118 Building multiple platforms in parallel 119 --------------------------------------- 120 121 When you want to compile Apache for multiple platforms in parallel it is 122 useful to share the source tree (usually via NFS, AFS or DFS) but build the 123 object files in separated subtrees. This can be accomplished by letting 124 APACI create a source shadow tree and build there: 125 126 $ ./configure --shadow --prefix=/path/to/apache 127 $ make 128 $ make install 129 130 Then APACI first determines the GNU platform triple, creates a shadow tree 131 in src.<gnu-triple> plus corresponding Makefile.<gnu-triple> and then 132 performs the complete build process inside this shadow tree. 133 134 Dynamic Shared Object (DSO) support 135 ----------------------------------- 136 137 Apache 1.3 supports building modules as shared objects on all major Unix 138 platforms (see section "Supported Platforms" in document 139 htdocs/manual/dso.html for details). APACI has a nice way of enabling the 140 building of DSO-based modules and automatically installing them: 141 142 $ ./configure --prefix=/path/to/apache \ 143 --enable-module=rewrite \ 144 --enable-shared=rewrite 145 $ make 146 $ make install 147 148 This builds and installs Apache with the default configuration except that 149 it adds the mod_rewrite module and automatically builds and installs it as a 150 DSO, so it is optionally available for loading under runtime. To make your 151 life even more easy APACI additionally inserts a corresponding `LoadModule' 152 line into the httpd.conf file in the installation phase. 153 154 APACI also supports a variant of the --enable-shared option: 155 156 $ ./configure --prefix=/path/to/apache \ 157 --enable-shared=max 158 $ make 159 $ make install 160 161 This enables shared object building for the maximum of modules, i.e. all 162 enabled modules (--enable-module or the default set) except for mod_so 163 itself (the bootstrapping module for DSO support). So, to build a 164 full-powered Apache with maximum flexibility by building and installing most 165 of the modules, you can use: 166 167 $ ./configure --prefix=/path/to/apache \ 168 --enable-module=most \ 169 --enable-shared=max 170 $ make 171 $ make install 172 173 This first enables most of the modules (all modules except some problematic 174 ones like mod_auth_db which needs third party libraries not available on 175 every platform or mod_log_agent and mod_log_referer which are deprecated) 176 and then enables DSO support for all of them. This way you get all these 177 modules installed and you then can decide under runtime (via the 178 `LoadModule') directives which ones are actually used. This is especially 179 useful for vendor package maintainers to provide a flexible Apache package. 180 181 On-the-fly added additional/private module 182 ------------------------------------------ 183 184 For Apache there are a lot of modules flying around on the net which solve 185 particular problems. For a good reference see the Apache Module Registory at 186 http://modules.apache.org/ and the Apache Group's contribution directory at 187 http://www.apache.org/dist/contrib/modules/. These modules usually come in a 188 file named mod_foo.c. APACI supports adding these sources on-the-fly to the 189 build process: 190 191 $ ./configure --prefix=/path/to/apache \ 192 --add-module=/path/to/mod_foo.c 193 $ make 194 $ make install 195 196 This automatically copies mod_foo.c to src/modules/extra/, activates it in 197 the configuration and builds Apache with it. A very useful way is to combine 198 this with the DSO support: 199 200 $ ./configure --prefix=/path/to/apache \ 201 --add-module=/path/to/mod_foo.c \ 202 --enable-shared=foo 203 $ make 204 $ make install 205 206 This builds and installs Apache with the default set of modules, but 207 additionally builds mod_foo as a DSO and adds a `LoadModule' line to the 208 httpd.conf file to activate it for loading under runtime. 209 210 Apache and mod_perl 211 ------------------- 212 213 The Apache/Perl integration project (http://perl.apache.org/) from Doug 214 MacEachern <dougm (a] perl.apache.org> is a very powerful approach to integrate 215 a Perl 5 interpreter into the Apache HTTP server both for running Perl 216 programs and for programming Apache modules in Perl. The distribution 217 mod_perl-1.XX.tar.gz can be found on http://perl.apache.org/src/. Here is 218 how you can build and install Apache with mod_perl: 219 220 $ gunzip <apache_1.3.X.tar.gz | tar xvf - 221 $ gunzip <mod_perl-1.XX.tar.gz | tar xvf - 222 $ cd mod_perl-1.XX 223 $ perl Makefile.PL APACHE_SRC=../apache_1.3.X/src \ 224 DO_HTTPD=1 USE_APACI=1 \ 225 [EVERYTHING=1 ...] 226 $ make 227 $ make install 228 229 [optionally you now have the chance to prepare or add more 230 third-party modules to the Apache source tree] 231 232 $ cd ../apache_1.3.X 233 $ ./configure --prefix=/path/to/apache \ 234 --activate-module=src/modules/perl/libperl.a \ 235 [--enable-shared=perl] 236 $ make 237 $ make install 238 239 Apache and PHP 240 -------------- 241 242 The PHP language (http://www.php.net) is an HTML-embedded scripting language 243 which can be directly integrated into the Apache HTTP server for powerful HTML 244 scripting. The package can be found at http://www.php.net/downloads.php 245 246 1. How you can install Apache with a statically linked PHP: 247 248 $ gunzip <apache_1.3.X.tar.gz | tar xvf - 249 $ gunzip <php-3.0.tar.gz | tar xvf - 250 $ cd apache_1.3.X 251 $ ./configure --prefix=/path/to/apache 252 $ cd ../php-3.0 253 $ ./configure --with-apache=../apache_1.3.X 254 $ make 255 $ make install 256 257 [optionally you now have the chance to prepare or add more 258 third-party modules to the Apache source tree] 259 260 $ cd ../apache_1.3.X 261 $ ./configure --prefix=/path/to/apache \ 262 --activate-module=src/modules/php3/libphp3.a 263 $ make 264 $ make install 265 266 2. You can also use APXS: 267 268 $ cd apache-1.3.X 269 $ ./configure --prefix=/path/to/apache --enable-shared=max 270 $ make 271 $ make install 272 273 $ cd php-3.0.X 274 $ ./configure --with-apxs=/path/to/apache/bin/apxs \ 275 --with-config-file-path=/path/to/apache 276 $ make 277 $ make install 278 279 At this point don't forget to edit your conf/httpd.conf file and 280 make sure the file contains the line for PHP 3: 281 282 AddType application/x-httpd-php3 .php3 283 284 Or this line for PHP 4: 285 286 AddType application/x-httpd-php .php 287 288 Then restart your server. 289
Indexes created Tue Nov 24 01:28:34 UTC 2009
Terms of Use |
Privacy |
Trademarks |
Copyright Policy |
Site Guidelines |
Help
Your use of this web site or any of its content or software indicates your agreement to be bound by these Terms of Use.
Copyright © 1995-2008 Sun Microsystems, Inc.