all_in_one.html.en revision 90e0f7946d156746192720014bfcbe60de379b94
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
This file is generated from xml source: DO NOT EDIT
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-->
<title>Frequently Asked Questions - Apache HTTP Server</title>
<link href="/style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
<link href="/style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
<body id="manual-page"><div id="page-header">
<p class="menu"><a href="/mod/">Modules</a> | <a href="/mod/directives.html">Directives</a> | <a href="/faq/">FAQ</a> | <a href="/glossary.html">Glossary</a> | <a href="/sitemap.html">Sitemap</a></p>
<p class="apache">Apache HTTP Server Version 2.1</p>
<div id="path">
<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs-project/">Documentation</a> > <a href="../">Version 2.1</a> > <a href="./">FAQ</a></div><div id="page-content"><div id="preamble"><h1>Frequently Asked Questions</h1>
<div class="toplang">
<p><span>Available Languages: </span><a href="/en/faq/all_in_one.html" title="English"> en </a> |
<a href="/ja/faq/all_in_one.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> |
<a href="/ko/faq/all_in_one.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p>
</div>
<p>The latest version of this FAQ is always available from the main Apache
web site, at <<a href="http://httpd.apache.org/docs-2.1/faq/">http://httpd.apache.org/docs-2.1/faq/</a>>.</p>
<p>Since Apache 2.0 is quite new, we don't yet know what the <em>Frequently
Asked Questions</em> will be. While this section fills up, you should also
consult the <a href="http://httpd.apache.org/docs/misc/FAQ.html">Apache 1.3
FAQ</a> to see if your question is answered there.</p>
</div>
<div id="quickview"><ul id="toc"><li><img alt="" src="/images/down.gif" /> <a href="#topics">Topics</a></li>
</ul></div>
<div class="section">
<h2><a id="topics" name="topics">Topics</a></h2>
<dl><dt><a href="#background">Background</a></dt><dd>Background information about the Apache HTTP Server.</dd>
<dt><a href="#support">Support</a></dt><dd>What do I do when I have problems?</dd>
<dt><a href="#error">Error Messages</a></dt><dd>What does this error message mean?</dd>
<div class="section">
<h2><a name="background" id="background">Background</a></h2>
<ul>
Server?</a></li>
Apache?</a></li>
product or Web site?</a></li>
</ul>
<p>The Apache Software Foundation (ASF) is a 501(c)3 non-profit
organization, originating from the development of the Apache HTTPD
Server. For details on the history of the ASF, please see the
<a href="">Foundation FAQ</a></p>
<h3><a name="background.what-is-httpd" id="background.what-is-httpd">What is the Apache HTTP Server?</a></h3>
<ul>
<li>is highly configurable and extensible with third-party modules</li>
<li>can be customised by writing 'modules' using the Apache module
API</li>
<li>provides full source code and comes with an
<a href="http://www.apache.org/licenses/LICENSE-2.0">unrestrictive
license</a></li>
and most versions of Unix, as well as several other operating
systems</li>
<li>is actively being developed</li>
<li>encourages user feedback through new ideas, bug reports and
patches</li>
</ul>
<p>Apache is run on millions of Internet servers.
It has been tested thoroughly by both developers and users. The Apache
HTTP Server Project maintains rigorous standards before releasing new
versions of our server, and our server runs without a hitch on over
70% of all WWW servers available on the Internet. When bugs do show
up, we release patches and new versions as soon as they are
available.</p>
<p>You may <em>NOT</em> use any original artwork from the Apache
Software Foundation, nor make or use modified versions of such
artwork, except under the following conditions:</p>
<ul>
graphic</a> on a Web site that is being served by the Apache HTTP
server software.</li>
<li>You may use the aforementioned <a href="http://httpd.apache.org/docs/apache_pb.gif">'Powered by Apache'
Foundation logo</a> in product description and promotional material
<em>IF and ONLY IF</em> such use can in no way be interpreted as
anything other than an attribution. Using the Apache name and
artwork in a manner that implies endorsement of a product or
service is <a href="">strictly forbidden.</a></li>
</ul>
<p>For details, or related issues, please contact the Apache Software
Foundation's <a href="">Public Relations Committee</a>.</p>
<div class="section">
<h2><a name="support" id="support">Support</a></h2>
<ul>
to do in case of problems</a></li>
</ul>
<h3><a name="support.what2do" id="support.what2do">"Why can't I ...? Why won't ... work?" What to do in case of
problems</a></h3>
<p>If you are having trouble with your Apache server software, you should
take the following steps:</p>
<dl>
<dt>Check the ErrorLog!</dt>
<dd>Apache tries to be helpful when it encounters a problem. In many
cases, it will provide some details by writing one or more messages to the
server error log. Sometimes this is enough for you to diagnose & fix
the problem yourself (such as file permissions or the like). The default
location of the error log is
<code>/usr/local/apache2/logs/error_log</code>, but see the <code class="directive"><a href="/mod/core.html#errorlog">ErrorLog</a></code> directive in your config files for the
location on your server.</dd>
<dt>Check the ErrorLog again!</dt>
<dd>Nearly all problems can be solved by reading the error log.</dd>
<dd>The latest version of the Apache Frequently-Asked Questions list can
always be found at the main Apache web site.</dd>
<dt>Check the Apache bug database</dt>
<dd>Most problems that get reported to The Apache Group are recorded in
<strong>Please</strong> check the existing reports, open
<strong>and</strong> closed, before adding one. If you find that your
issue has already been reported, please <em>don't</em> add a "me, too"
report. If the original report isn't closed yet, we suggest that you
check it periodically. You might also consider contacting the original
submitter, because there may be an email exchange going on about the
issue that isn't getting recorded in the database.</dd>
<dt><a id="support.what2do.user-support" name="support.what2do.user-support">Ask in a user support forum</a></dt>
<dd><p>Apache has an active community of users who are willing to share
their knowledge. Participating in this community is usually the best and
fastest way to get answers to your questions and problems.</p>
mailing list</a></p>
user support issues.</p>
</dd>
<dt>Please use the bug database for bugs!</dt>
<dd><p>If you've gone through those steps above that are appropriate and
have obtained no relief, then please <em>do</em> let the httpd developers
know about the problem by <a href="http://httpd.apache.org/bug_report.html">logging a bug
report</a>.</p>
<p>If your problem involves the server crashing and generating a core
dump, please <a href="http://httpd.apache.org/dev/debugging.html">
include a backtrace</a> (if possible).</p>
</dd>
</dl>
<p>With millions of users and fewer than sixty volunteer developers,
we cannot provide personal support for Apache. For free support, we
<p>Professional, commercial support for Apache is available from
<a href="http://www.apache.org/info/support.cgi">a number of
companies</a>.</p>
<div class="section">
<h2><a name="error" id="error">Error Messages</a></h2>
<ul>
core_output_filter: writing data to the network</a></li>
headers</a></li>
</ul>
core_output_filter: writing data to the network</a></h3>
<p>Apache uses the <code>sendfile</code> syscall on platforms
where it is available in order to speed sending of responses.
Unfortunately, on some systems, Apache will detect the presence of
<code>sendfile</code> at compile-time, even when it does not work
properly. This happens most frequently when using network or
other non-standard file-system.</p>
<p>Symptoms of this problem include the above message in the error
log and zero-length responses to non-zero-sized files. The
problem generally occurs only for static files, since dynamic
content usually does not make use of <code>sendfile</code>.</p>
<p>To fix this problem, simply use the <code class="directive"><a href="/mod/core.html#enablesendfile">EnableSendfile</a></code> directive to disable
<code>sendfile</code> for all or part of your server. Also see
help with similar problems.</p>
<p>If you get error messages related to the <code>AcceptEx</code> syscall
on win32, see the <code class="directive"><a href="/mod/mpm_winnt.html#win32disableacceptex">Win32DisableAcceptEx</a></code>
directive.</p>
headers</a></h3>
<p>Most problems with CGI scripts result in this message written in the
error log together with an <code>Internal Server Error</code> delivered
to the browser. A guide to helping debug this type of problem is
tutorial</a>.</p>
</div></div>
<div class="bottomlang">
<p><span>Available Languages: </span><a href="/en/faq/all_in_one.html" title="English"> en </a> |
<a href="/ja/faq/all_in_one.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> |
<a href="/ko/faq/all_in_one.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p>
</div><div id="footer">
<p class="apache">Copyright 1995-2005 The Apache Software Foundation or its licensors, as applicable.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p>
<p class="menu"><a href="/mod/">Modules</a> | <a href="/mod/directives.html">Directives</a> | <a href="/faq/">FAQ</a> | <a href="/glossary.html">Glossary</a> | <a href="/sitemap.html">Sitemap</a></p></div>
</body></html>