⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 asg01.htm

📁 apache技术手册
💻 HTM
📖 第 1 页 / 共 2 页
字号:
<HTML>

<HEAD>

<TITLE>Apache Server Survival Guide asg01.htm </TITLE>

<LINK REL="ToC" HREF="index.htm" tppabs="http://docs.rinet.ru:8080/Apachu/index.htm">

<LINK REL="Index" HREF="htindex.htm" tppabs="http://docs.rinet.ru:8080/Apachu/htindex.htm">

<LINK REL="Next" HREF="asg02.htm" tppabs="http://docs.rinet.ru:8080/Apachu/asg02.htm">

<LINK REL="Previous" HREF="asgpt1.htm" tppabs="http://docs.rinet.ru:8080/Apachu/asgpt1.htm"></HEAD>

<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" VLINK="#800080">
<!--#exec cmd="/www/docs/ssi-bin/restricted_search.ssi"-->





<!--#exec cmd="/www/docs/ssi-bin/inc.ssi"-->






<A NAME="I0"></A>

<H2>Apache Server Survival Guide asg01.htm</H2>

<P ALIGN=LEFT>

<A HREF="asgpt1.htm" tppabs="http://docs.rinet.ru:8080/Apachu/asgpt1.htm" TARGET="_self"><IMG SRC="purprev.gif" tppabs="http://docs.rinet.ru:8080/Apachu/purprev.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Previous Page"></A>

<A HREF="index.htm" tppabs="http://docs.rinet.ru:8080/Apachu/index.htm" TARGET="_self"><IMG SRC="purtoc.gif" tppabs="http://docs.rinet.ru:8080/Apachu/purtoc.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="TOC"></A>

<A HREF="asg02.htm" tppabs="http://docs.rinet.ru:8080/Apachu/asg02.htm" TARGET="_self"><IMG SRC="purnext.gif" tppabs="http://docs.rinet.ru:8080/Apachu/purnext.gif" WIDTH = 32 HEIGHT = 32 BORDER = 0 ALT="Next Page"></A>


<HR ALIGN=CENTER>

<P>

<UL>

<UL>

<UL>

<LI>

<A HREF="#E68E1" >What Is a Web Server?</A>

<LI>

<A HREF="#E68E2" >Commercial Versus Freeware</A>

<LI>

<A HREF="#E68E3" >Ease of Installation</A>

<LI>

<A HREF="#E68E4" >Ease of Configuration</A>

<LI>

<A HREF="#E68E5" >Ease of Extending or Customizing Some Aspect of the Server</A>

<LI>

<A HREF="#E68E6" >Features</A>

<LI>

<A HREF="#E68E7" >Size of the Installed Base</A>

<LI>

<A HREF="#E68E8" >Ongoing Development</A>

<LI>

<A HREF="#E68E9" >Performance and Resource Consumption</A>

<LI>

<A HREF="#E68E10" >Secure Transaction Support</A>

<LI>

<A HREF="#E68E11" >Source Code Availability</A>

<LI>

<A HREF="#E68E12" >Technical Support</A>

<LI>

<A HREF="#E68E13" >Third-Party Support</A>

<LI>

<A HREF="#E68E14" >Summary</A></UL></UL></UL>

<HR ALIGN=CENTER>

<A NAME="E66E1"></A>

<H1 ALIGN=CENTER>

<CENTER>

<FONT SIZE=6 COLOR="#FF0000"><B>1</B></FONT></CENTER></H1>

<BR>

<A NAME="E67E3"></A>

<H2 ALIGN=CENTER>

<CENTER>

<FONT SIZE=6 COLOR="#FF0000"><B>Why the Apache Server?</B></FONT></CENTER></H2>

<BR>

<BR>

<A NAME="E68E1"></A>

<H3 ALIGN=CENTER>

<CENTER>

<FONT SIZE=5 COLOR="#FF0000"><B>What Is a Web Server?</B></FONT></CENTER></H3>

<BR>

<P>A Web server is the server software behind the World Wide Web. It listens for requests from a client, such as a browser like Netscape or Microsoft's Internet Explorer. When it gets one, it processes that request and returns some data. This data usually takes the form of a formatted page with text and graphics. The browser then renders this data to the best of its ability and presents it to the user. Web servers are in concept very simple programs. They await for requests and fulfill them when received.

<BR>

<P>Web servers communicate with browsers or other clients using the Hypertext Transfer Protocol (HTTP), which is a simple protocol that standardizes the way requests are sent and processed. This allows a variety of clients to communicate with any vendor's server without compatibility problems.

<BR>

<P>Most of the documents requested are formatted using Hypertext Markup Language (HTML). HTML is a small subset of another markup language called Standard General Markup Language (SGML), which is in wide use by many organizations and the U.S. Government.

<BR>

<P>HTML is the lifeblood of the Web. It is a simple markup language used for formatting text. Browsers interpret the markup information and render its intent to the best of their abilities. More importantly, HTML allows linking to different documents and resources; this is the hypertext portion of the Web.

<BR>

<P>Hypertext allows a user to refer to other documents stored in the same computer or in a computer located in a different part of the world. It allows information to be almost tridimensional. Not only can you read sequentially, but you can jump for more elsewhere.

<BR>

<P>The information retrieval process is completely transparent to the user; it's easy and free-form. Navigation through this sea of information is in an ad hoc way. While the results and implications of this new learning process are yet to be seen, it sure is powerful. It provides a seamless exploration experience of documents and services. This is what the Web is all about. It allows you to gather information easily and presents it in a way that it is easy to digest. It's graphic, and it can combine sound and moving pictures.

<BR>

<P>You can learn more and find related issues that spark your interest; it's interactive. Instead of paging through a book (still a good thing), you can use the computer to remove much of the legwork associated with retrieving related information, and it allows you to explore the material that fits your needs or mood. It's like TV, but you get to choose the programming.

<BR>

<P>The Web server is responsible for fetching you this information. While Web servers may have been simple at some point, they are not anymore. All Web servers are not created equal.

<BR>

<P>If all the sudden you were asked to set up a Web site, you would be confronted with a variety of issues that you would need to resolve before you code your first HTML page. The most important issue, and probably the reason why you bought this book, is deciding which server software to use. Given the myriad of Web servers available, the choice is undoubtedly difficult.

<BR>

<P>The following is a list of issues that you should use to evaluate any piece of software before you commit work to it:

<BR>

<UL>

<UL>

<P>Commercial versus freeware

</UL></UL>

<UL>

<UL>

<P>Ease of installation

</UL></UL>

<UL>

<UL>

<P>Ease of configuration

</UL></UL>

<UL>

<UL>

<P>Ease of extending or customizing some aspect of the server

</UL></UL>

<UL>

<UL>

<P>Features

</UL></UL>

<UL>

<UL>

<P>Size of the installed base

</UL></UL>

<UL>

<UL>

<P>Ongoing development

</UL></UL>

<UL>

<UL>

<P>Performance and resource consumption

</UL></UL>

<UL>

<UL>

<P>Secure transaction support

</UL></UL>

<UL>

<UL>

<P>Source code availability

</UL></UL>

<UL>

<UL>

<P>Technical support

</UL></UL>

<UL>

<UL>

<P>Platform support

</UL></UL>

<UL>

<UL>

<P>Third-party support

<BR>

</UL></UL>

<BR>

<A NAME="E68E2"></A>

<H3 ALIGN=CENTER>

<CENTER>

<FONT SIZE=5 COLOR="#FF0000"><B>Commercial Versus Freeware</B></FONT></CENTER></H3>

<BR>

<P>Apache is freeware; therefore, you invariably have to confront the issue of free software. Is free software really cheap? After all, who do you go to if you have problems? What are the odds of the product not being supported? Free software usually has sparse documentation and no direct technical support. However, there are a few software packages out there that are superbly documented, supported, and maintained. In my view, Apache belongs to that list.

<BR>

<BR>

<A NAME="E68E3"></A>

<H3 ALIGN=CENTER>

<CENTER>

<FONT SIZE=5 COLOR="#FF0000"><B>Ease of Installation</B></FONT></CENTER></H3>

<BR>

<P>If you have a little understanding about UNIX, know how to use an UNIX editor such as vi, pico, or emacs, and are not afraid of the shell, Apache is a great choice. It is easy to install and configure, even for people that are not too savvy on the UNIX ways. The software is available in two types: precompiled and in source form.

<BR>

<P>Precompiled binaries are available for

<BR>

<UL>

<LI>AUX 3.1

<BR>

<BR>

<LI>BSDI 2.0

<BR>

<BR>

<LI>FreeBSD 2.1

<BR>

<BR>

<LI>HP-UX 9.07

<BR>

<BR>

<LI>IRIX 5.3

<BR>

<BR>

<LI>Linux

<BR>

<BR>

<LI>NetBSD 1.1

<BR>

<BR>

<LI>NEXTSTEP

<BR>

<BR>

<LI>SolarisX86 2.5

<BR>

<BR>

<LI>Solaris 2.4

<BR>

<BR>

<LI>Solaris 2.5

<BR>

<BR>

<LI>SunOS 4.1.3

<BR>

<BR>

<LI>UnixWare 1.1.2

<BR>

<BR>

</UL>

<P>There's also an OS/2 version. Rumor has it that a Windows NT version of Apache is also in the works. Given the growing popularity of both Apache and Windows NT in corporate networks, such a port would help to capture an even bigger segment of the Web server market.

<BR>

<P>If your OS/hardware is not available precompiled and you have an UNIX compiler such as GNU's GCC, there are configuration directives for almost every UNIX variant imaginable. All you need to do is set up a few options, type make, and your software will be built. The next chapter walks you through the process of compiling and installing your Apache server.

<BR>

<P>Installing a Web server&#151;be it through a graphical user interface (GUI)-based Netscape product or Apache&#151;is simple. The GUI tools may give more reassurance to people who are afraid of command line interfaces, but in general, configuration and installation are fairly straight forward in either version. If you are not sure what a configuration value is, more than likely you will be stumped in either presentation. This is where documentation, such as this book, will help you. This book doesn't assume that you know much about UNIX or anything else. However, it will give you enough background to get going and will enlighten you about some of the possibilities. I hope your curiosity awakens.

<BR>

<BR>

<A NAME="E68E4"></A>

<H3 ALIGN=CENTER>

<CENTER>

<FONT SIZE=5 COLOR="#FF0000"><B>Ease of Configuration</B></FONT></CENTER></H3>

<BR>

<P>Configuring Apache is very easy to do. Apache utilizes three configuration files; all of which are already preset to safe default behaviors. You just need to specify a fe<A NAME="I2"></A>w file locations, and name your server so that Apache can find its configuration files and the location of the document tree it is serving. To do this, all you need is a good UNIX text editor that you feel comfortable with. Chances are your version of UNIX has some sort of graphical editor you already feel comfortable with. <A HREF="asg02.htm" tppabs="http://docs.rinet.ru:8080/Apachu/asg02.htm">Chapter 2</A>, &quot;Installing and Configuring an Apache Server,&quot; explains all the basic configuration steps you need to take to get your Apache server running fast. It's easy to do.

<BR>

<BR>

<A NAME="E68E5"></A>

<H3 ALIGN=CENTER>

<CENTER>

<FONT SIZE=5 COLOR="#FF0000"><B>Ease of Extending or Customizing Some Aspect of the Server</B></FONT></CENTER></H3>

<BR>

<P>If you are customizing some aspect of the server, you'll love Apache. Its source code is clearly written but is a little thin on the documentation side. The Apache server is implemented as a set of software modules. Creating a new module that modifies the behavior of the server in some way will require less to learn on your part. There's a growing list of freely available third-party modules. More than likely you can find a module that implements the functionality you need.

<BR>

<BR>

<A NAME="E68E6"></A>

<H3 ALIGN=CENTER>

<CENTER>

<FONT SIZE=5 COLOR="#FF0000"><B>Features</B></FONT></CENTER></H3>

<BR>

<P>The Apache server implements the same, if not more, features than the equivalent commercial Web server, and basically every aspect of the Apache server's functionality is configurable. This makes it easy to get the server to behave the way you want or need for your site.

<BR>

<P>Some of the most important features include the following:

<BR>

<UL>

<LI>It's a plug-and-play replacement for NCSA Web servers.

<BR>

<BR>

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -