View apache versions in linux

For the apache version in linux, refer to rpm-qa httpd to Upgrade apache. To Help You Upgrade Apache, we have compiled a document to introduce some important information about apache users. We would like to remind you that this document only describes the changes that have occurred during the last update, and the same is recommended for example. Therefore, if you are using Apache1.1 or an older version, you must first understand the changes made before these versions are upgraded to 1.2, and then consider using this document. Users of earlier versions can view the src/CHANGES file, which records previous code CHANGES. This document is just a summary of some important points. For more details, you can find it in the New Feature document, or you can view the src/CHANGES file. Configuration changes during compilation · the original code is reorganized. This will affect the personal configuration module and individual modification of other configurations. In addition, the Module boot (directive) is changed to the AddModule boot (directive ). · Change the configuration variable EXTRA_LFLAGS to EXTRA_LDFALGS. ·-The DMAIMUM_DNSA definition is deleted. If necessary, you can use mod_access to perform bidirectional DNS lookup. ·-DSERVER_SUBVERSION = \ "string \" the configuration option during compilation is called "ap_add_version_component? Is replaced by the API. At the same time, the server can no longer be compiled by configuring scripts during compilation. · Mod_dir is divided into mod_autoindex and mod_dir. · Mod_browser is replaced by mod_setenvif. · In the IRIX system, if untrustworthy users are included, they can write CGI with the same user name as httpd during execution, consider using suexec or adding DUSE_FCNTL_SERIALIZED_ACCEPT to EXTRA_CFLAGS. This is a little slower. More explanations can be found in the performance tuning page. Under the default configuration, there is only one mild protection for possible service attack attacks. However, this configuration runs very fast. · Mod_auth_msql has been deleted from this version. · The New Apache automatic configuration Interface (Apache Autoconf-style Interface) APACI is added to the top layer, it provides a real black box building and installation process for the complete Apache Software Package. Compile and install Apache 1.3 This document covers how to compile and install Apache On Unix systems, and how to manually create and install Apache. if you want to use the automatic configuration interface, you should read the INSTALL file under the root directory of the Apache source code release. if you install it on a specific platform, see? Using Apache with Microsoft Windows? Using Apache with Novell Netware 5? Using Apache with hp mpe/iX? Compiling Apache under UnixWare? Overview of the Apache TPF Port to download the latest Apache version information can be found on the Apache web Server http://www.apache.org. it lists the current version, the current beta version, and some image web sites and anonymous ftp sites .. if you download an executable release, you can directly jump to install Apache. otherwise, read the next section and compile the Apache server. three steps are required to compile Apache: first, select the Apache module you want to include. create a configuration for your operating system. finally, compile the executable file. all configuration work is completed under the src directory of the Apache release. change it to the current directory. 1. in the configuration file, select the module to be compiled into Apache. the Rows without comments correspond to the optional modules you want to add (between the AddModule rows and at the bottom of the file ), or add new lines of additional modules corresponding to the ones you downloaded or wrote. (For details about how to compile the preliminary Apache module, see API.html ). if you are sure that you do not need some default modules, you can comment them out (although so, be careful, because many default modules are very important for proper operation and server security ). you must also read the instructions in the configuration file to determine whether you need these policies. 2. configure Apache for your operating system. generally, you only need to run the Configure script as follows. however, if this fails or you have some special requirements (for example, including an additional library required by an optional module), you may need to edit one or more of the following options in the configuration file: EXTRA_CFLAGS, LIBS, LDFLAGS, INCLUDES. run the Configure configuration script: % Configure Using 'configuration' as config file + configured for <whatever> platform + setting C compiler to <whatever> * + setting C compiler optimization-level to <whatever> * + Adding selected modules + doing sanity check on compiler and options Creating Makefile in support Creating Makefile in main Creating Makefile in OS/unix Creating Makefile in modules/standard (*: depending on your configuration file and system, Configure may not print these rows. that is also normal ). this generates a Makefile file for Step 3. A Makefile file is also generated for the optional support Program in the support directory. (if you want to maintain multiple configurations, you can give Configure an option to tell it which alternative Configuration file to read, such as Configure-file Configuration. ai ). 3. type make. the modules we put into the Apache release are tested and used by different members of the development team. some modules developed by members or third parties for special occasions can be obtained. the following describes how to connect the blockchain to Apache core code. to install Apache, you should now have an executable file named httpd In the src directory. the executable Apache release contains this file. the next step is to install the program and configure it. apache is designed to be configured and run in the same directory as during compilation. if you want to run it elsewhere, create a directory and copy the conf, logs, and icons directories. in either case, you must read security tips to know how to set permissions for the root directory of the server. in the next step, edit the configuration file for the server. this includes setting different commands (directives) in three major configuration files ). by default, these files are named srm in the conf directory. conf, access. conf and httpd. conf. to help you get started, the conf directory of the release has the same file called srm. conf-dist, access. conf-dist and httpd. conf-dist. copy or rename these files to remove-dist. edit these files. carefully read the comments in each file. setting these files incorrectly will make your server unavailable or insecure. you should also have mime in the conf directory. types additional file. this file does not need to be edited.