apache怎么用_apache jmeter教程

英文原文网址：https://httpd.apache.org/docs/2.4/getting-started.html

翻译方法：google translate翻译后，本人重新校对。感触是，不得不说google翻译准得惊人，准确率超过95%，我的改动不超过一百字。但是确实没有达到完全代替人工的程度。

If you're completely new to the Apache HTTP Server, or even to running a website at all, you might not know where to start, or what questions to ask. This document walks you through the basics.

如果您完全是Apache HTTP Server的新手，或者从未运行过一个网站，您可能不知道从哪里开始，或者不知道要问什么问题。本文将引导您了解基础知识。

Clients, Servers, and URLs

Addresses on the Web are expressed with URLs - Uniform Resource Locators - which specify a protocol (e.g. http), a servername (e.g. www.apache.org), a URL-path (e.g./docs/current/getting-started.html), and possibly a query string (e.g. ?arg=value) used to pass additional arguments to the server.

A client (e.g., a web browser) connects to a server (e.g., your Apache HTTP Server), with the specified protocol, and makes a request for a resource using the URL-path.

The URL-path may represent any number of things on the server. It may be a file (like getting-started.html) a handler (like server-status) or some kind of program file (like index.php). We'll discuss this more below in the Web Site Content section.

The server will send a response consisting of a status code and, optionally, a response body. The status code indicates whether the request was successful, and, if not, what kind of error condition there was. This tells the client what it should do with the response. You can read about the possible response codes in HTTP Server wiki.

Details of the transaction, and any error conditions, are written to log files. This is discussed in greater detail below in the Logs Files and Troubleshooting section.

客户端，服务器和URL

Web上的地址是以URL（统一资源定位符）的形式给出的。URL指定了协议（例如http），服务器名称（例如www.apache.org），URL路径（例如/docs/current/getting-started.html），也可能是一个查询字符串（例如?arg=value），用于将额外的参数传递给服务器。

客户端（例如，Web浏览器）使用指定的协议连接到服务器（例如，您的Apache HTTP Server），并使用URL路径请求资源。

URL路径可以表示服务器上的任何数量的东西。它可能是一个文件（如getting-started.html）一个处理程序（如服务器状态）或某种程序文件（如index.php）。我们将在“ 网站内容”部分中详细讨论。

服务器将发送由状态码和可选的响应主体组成的响应。状态代码指示请求是否成功，如果没有成功，则会指示出现了什么样的错误状况。这告诉客户端接下来该做什么。您可以阅读HTTP Server wiki中可能的响应代码。

事务的详细信息和任何错误条件都将写入日志文件。这将在日志文件和故障排除部分中详细讨论。

Hostnames and DNS

In order to connect to a server, the client will first have to resolve the servername to an IP address - the location on the Internet where the server resides. Thus, in order for your web server to be reachable, it is necessary that the servername be in DNS.

If you don't know how to do this, you'll need to contact your network administrator, or Internet service provider, to perform this step for you.

More than one hostname may point to the same IP address, and more than one IP address can be attached to the same physical server. Thus, you can run more than one web site on the same physical server, using a feature called virtual hosts.

If you are testing a server that is not Internet-accessible, you can put host names in your hosts file in order to do local resolution. For example, you might want to put a record in your hosts file to map a request for www.example.com to your local system, for testing purposes. This entry would look like:

127.0.0.1 www.example.com

A hosts file will probably be located at /etc/hosts or C:\\Windows\\system32\\drivers\\etc\\hosts.

You can read more about the hosts file at Wikipedia.org/wiki/Hosts_(file), and more about DNS at Wikipedia.org/wiki/Domain_Name_System.

主机名和DNS

为了连接到服务器，客户端首先必须将servername解析为IP地址 - 服务器在Internet上的位置。因此，为了使您的Web服务器可访问，服务器名称必须位于DNS中。

如果您不知道如何执行此操作，则需要联系您的网络管理员或Internet服务提供商，为您执行此步骤。

多个主机名可能指向相同的IP地址，并且可以将多个IP地址附加到同一物理服务器。因此，您可以使用称为虚拟主机的功能在同一物理服务器上运行多个网站。

如果您正在测试Internet访问不了的服务器，则可以在主机文件中放置主机名，以便进行本地解析。例如，您可能希望在主机文件中添加一个记录，将对www.example.com的请求映射到本地系统，以进行测试。这个记录可能写成这样：

127.0.0.1 www.example.com

主机文件可能位于/etc/hosts或C:\\Windows\\system32\\drivers\\etc\\hosts。

您可以在Wikipedia.org/wiki/Hosts_(file）上了解有关hosts文件的更多信息，以及有关Wikipedia.org/wiki/Domain_Name_System的 DNS的更多信息。

Configuration Files and Directives

The Apache HTTP Server is configured via simple text files. These files may be located any of a variety of places, depending on how exactly you installed the server. Common locations for these files may be found in the httpd wiki. If you installed httpd from source, the default location of the configuration files is /usr/local/apache2/conf. The default configuration file is usually called httpd.conf. This, too, can vary in third-party distributions of the server.

The configuration is frequently broken into multiple smaller files, for ease of management. These files are loaded via the Include directive. The names or locations of these sub-files are not magical, and may vary greatly from one installation to another. Arrange and subdivide these files as makes the most sense to you. If the file arrangement you have by default doesn't make sense to you, feel free to rearrange it.

The server is configured by placing configuration directives in these configuration files. A directive is a keyword followed by one or more arguments that set its value.

The question of "Where should I put that directive?" is generally answered by considering where you want a directive to be effective. If it is a global setting, it should appear in the configuration file, outside of any <Directory>, <Location>, <VirtualHost>, or other section. If it is to apply only to a particular directory, then it should go inside a <Directory>section referring to that directory, and so on. See the Configuration Sections document for further discussion of these sections.

In addition to the main configuration files, certain directives may go in .htaccess files located in the content directories. .htaccess files are primarily for people who do not have access to the main server configuration file(s). You can read more about .htaccess files in the .htaccess howto.

配置文件和指令

Apache HTTP Server通过简单的文本文件进行配置。这些文件可能处于不同的位置，具体取决于您如何安装服务器。这些文件的常见位置可以在httpd维基中找到。如果从源安装了httpd，则配置文件的默认位置为/usr/local/apache2/conf。默认配置文件通常称为httpd.conf。当然，这也可能因服务器的发行版不同而存在区别。（译者注：apache2 通过apt-get 安装 配置文件在/etc/apache2里。另外总体配置在apache2.conf中。）

配置经常被分成多个较小的文件，便于管理。这些文件通过Include指令加载。这些子文件的名称或位置不是固定的，并且可能由于安装的不同有很大差异。安排和细分这些文件对你来说是最有意义的。如果你认为默认的文件安排有什么不妥，请随意重新排列组合。

我们通过在这些配置文件中放置配置指令来配置服务器。指令是一个关键字，后跟一个或多个设置其值的参数。

一般来说，“ 我应该在哪里提出这个指令？ ”这个问题的答案是：这要取决于你想要这个指令有怎样的作用域。如果是全局设置，它应该出现在总体配置文件中，而不应在<Directory>， <Location>， <VirtualHost>或其他部分。而如果只应用于特定的目录，那么它应该进入一个引用该目录的<Directory>部分，依此类推。有关这些部分的进一步讨论，请参阅配置部分文档。

除了主配置文件之外，某些指令也可能位于内容目录中的.htaccess文件中。.htaccess文件主要适用于无法访问主服务器配置文件的用户。您可以在.htaccess howto中阅读更多关于.htaccess文件的信息。

Web Site Content

Web site content can take many different forms, but may be broadly divided into static and dynamic content.

Static content is things like HTML files, image files, CSS files, and other files that reside in the filesystem. The DocumentRoot directive specifies where in your filesystem you should place these files. This directive is either set globally, or per virtual host. Look in your configuration file(s) to determine how this is set for your server.

Typically, a document called index.html will be served when a directory is requested without a file name being specified. For example, if DocumentRoot is set to /var/www/htmland a request is made for https://www.example.com/work/, the file /var/www/html/work/index.html will be served to the client.

Dynamic content is anything that is generated at request time, and may change from one request to another. There are numerous ways that dynamic content may be generated. Various handlers are available to generate content. CGI programs may be written to generate content for your site.

Third-party modules like mod_php may be used to write code that does a variety of things. Many third-party applications, written using a variety of languages and tools, are available for download and installation on your Apache HTTP Server. Support of these third-party things is beyond the scope of this documentation, and you should find their documentation or other support forums to answer your questions about them.

网站内容

网站内容可以采取许多不同的形式，但可以大致分为静态和动态内容。

静态内容是HTML文件，图像文件，CSS文件以及文件系统中的其他文件。 DocumentRoot指令指定文件系统中应该放置这些文件的位置。该指令是全局设置的，也可以是每个虚拟主机。查看您的配置文件以确定如何为您的服务器设置。

通常，当请求没有指定文件名的目录时，服务器将默认回应一个名为index.html的文档。例如，如果DocumentRoot设置为/var/www/html，并且请求是针对https://www.example.com/work/，则文件/var/www/html/work/index.html将被提供给客户端。

动态内容是在请求时生成的任何内容，不同的请求又不同的回应。有多种方式可以生成动态内容。各种处理程序可用于生成内容。你可能会编写CGI程序来为您的网站生成内容。

也可以使用第三方模块，如mod_php来编写执行各种操作的代码。许多使用各种语言和工具编写的第三方应用程序可以在您的Apache HTTP服务器上进行下载和安装。介绍这些第三方模块已经超出了本文档应该涵盖的范围，您可以找到相关文档或到其他支持论坛来解答您的疑问。

Log Files and Troubleshooting

As an Apache HTTP Server administrator, your most valuable assets are the log files, and, in particular, the error log. Troubleshooting any problem without the error log is like driving with your eyes closed.

The location of the error log is defined by the ErrorLog directive, which may be set globally, or per virtual host. Entries in the error log tell you what went wrong, and when. They often also tell you how to fix it. Each error log message contains an error code, which you can search for online for even more detailed descriptions of how to address the problem. You can also configure your error log to contain a log ID which you can then correlate to an access log entry, so that you can determine what request caused the error condition.

You can read more about logging in the logs documentation.

日志文件和故障排除

作为Apache HTTP Server管理员，您最宝贵的资产是日志文件，特别是错误日志。排除任何没有错误日志的问题，就像开车闭眼。

错误日志的位置由可以全局设置或每个虚拟主机设置的ErrorLog指令定义。错误日志中的条目告诉您出了什么问题，何时出现。他们经常也会告诉你如何解决它。每个错误日志消息包含一个错误代码，您可以在线搜索更详细的描述如何解决问题。您还可以将错误日志配置为包含一个日志ID，然后可以将其与访问日志条目相关联，以便您可以确定导致错误条件的请求。

您可以阅读有关登录日志文档的更多信息。