blocks|key|882226|text|httpd.conf是为用户配置而设计的。您确实不应该编辑apache2.conf，因为它可能会通过以后的升级而更新。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|882227|另一个选项是将您的自定义配置放到/etc/apache2/conf.d+.d中，这个目录中的所有文件都包括在内。|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|E|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|F|8|@]|9|@]|A|$]]]|D|$]]

The httpd.conf is designed for user configurations. You really should not edit the apache2.conf as it may be updated by future upgrades.

An additional option is to just put your custom configuration into /etc/apache2/conf.d, all files in this directory are included as well.

blocks|key|1918986|text|这不是你唯一的选择。在Ubuntu/Debian上，Apache还处理/etc/apache2/sites-enabled/中的所有文件(这应该是sites-available/目录中由a2ensite和a2dissite程序管理的文件的符号链接)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1918987|您打算为VirtualHosts使用这些目录。|entityMap^0|Z|R|21|G|2L|8|2U|9|0|4|B^^$0|@$1|2|3|4|5|6|7|I|8|@$9|J|A|K|B|C]|$9|L|A|M|B|C]|$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]]|H|$]]

These are not your only options. On Ubuntu/Debian, Apache also processes all the files in <code>/etc/apache2/sites-enabled/</code> (which should be symlinks to files in <code>sites-available/</code> directory, managed by the <code>a2ensite</code> and <code>a2dissite</code> programs)

You're intended to use these directories for <code>VirtualHost</code>s.

blocks|key|882608|text|发布了许多软件，其中一个是名为httpd的web服务器。httpd项目源包括一个httpd.conf示例配置文件，默认情况下它安装在/usr/local/etc/httpd或/etc/httpd中。在大多数系统上，您都会发现httpd是这样命名的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|882609|然而，很久很久以前，Debian+/Linux发行版中的某个人决定将该发行版中的软件名称从httpd更改为apache2。因此，在Debian系统上，您将在名为apache2.conf的目录中找到名为/etc/apache2的配置文件。我不知道是谁干的，也不知道为什么，但这是一个长期混乱的根源，就像把Windows称为“微软”或ESXi+"VMware“一样。基于Debian的发行版，比如Ubuntu，继承了这种奇怪的特性。更奇怪的是，它们还包括一个文件/etc/apache2/httpd.conf，它是来自apache2.conf的Included，用户可以在其中放置自定义配置。|882610|因此，答案是，如果你使用的是基于Debian的系统，你就会弯下脑筋去做Debian希望你做的事情。否则，您通常会像上游httpd项目那样以正常的方式进行操作。|entityMap^0|F|5|14|A|1U|K|2F|A|0|19|5|1H|7|28|C|2S|C|6D|N|75|C|7I|7|0^^$0|@$1|2|3|4|5|6|7|K|8|@$9|L|A|M|B|C]|$9|N|A|O|B|C]|$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]|$9|Y|A|Z|B|C]|$9|10|A|11|B|C]|$9|12|A|13|B|C]|$9|14|A|15|B|C]|$9|16|A|17|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|18|8|@]|D|@]|E|$]]]|J|$]]

The Apache Software Foundation publishes many bits of software, one of which is a web server named <code>httpd</code>. The httpd project sources include among other things an <code>httpd.conf</code> sample configuration file, which is installed by default in <code>/usr/local/etc/httpd</code> or <code>/etc/httpd</code>. You will find httpd named as such on most systems.

However, long ago and far away, someone in the Debian GNU/Linux distribution decided to change the name of the software within that distribution from <code>httpd</code> to <code>apache2</code>. Thus on a Debian system you will find a configuration file named <code>apache2.conf</code> in a directory named <code>/etc/apache2</code>. I don't know who did this or why, but it's a perennial source of confusion on par with calling Windows "Microsoft" or ESXi "VMware". Distributions based on Debian, such as Ubuntu, inherit this strangeness. Even stranger, they then include a file <code>/etc/apache2/httpd.conf</code> which is <code>Include</code>d from <code>apache2.conf</code> into which users can place custom configuration.

So the answer is, if you're on a Debian-based system, you bend your brain into doing things the way Debian wants you to do it. Otherwise you generally do things the normal way as the upstream httpd project does it.

blocks|key|882402|text|Apache+2.4+(在Debian/Ubuntu下)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|882403|用于配置/重写的|882404|(不一定是新站点)：|header-two|882405|在/etc/apache2/conf-available/{name}.conf中放置一个新的配置文件。|offset|length|style|CODE|882406|使用sudo+a2enconf+{name}或sudo+a2disconf+{name}启用/禁用新配置。|882407|这些命令中的指令也可以覆盖httpd.conf或apache2.conf，因为用户添加的任何附加配置文件都会在主配置之后最后读取。|882408|重新启动apache2服务以反映更改。|882409|用于站点的|882410|(以及任何特定于站点的配置重写)：|882411|在/etc/apache2/sites-available/{name}.conf中放置一个新的站点文件|882412|使用sudo+a2ensite+{name}或sudo+a2dissite+{name}启用/禁用站点配置。|882413|882414|不要使用：|882415|httpd.conf仍然作为主配置文件安装在某些Linux发行版上。在其他情况下，您不应该再看到它了--如果您希望通过包管理器干净/轻松地升级Apache，请将它保持为空，就像安装时一样。|882416|apache2.conf仍然安装在许多系统上，并用作Debian/Ubuntu的主要配置文件。但是，如果您希望干净/轻松地升级Apache，请不要使用它。您应该会在这个文件的底部看到一些站点和自定义配置的include语句。|882417|882418|用它们代替！|882419|根据Linux发行版的不同，可以通过Linux包管理器安装其中的一个或两个文件。这是一个很好的理由不去碰它们，因为它们可能会在将来的系统升级过程中被意外地覆盖。|882420|您可能在“全局”Apache2+2配置文件中看到的任何内容都可以在您的自定义配置下添加/覆盖，如上面所示。您还可以自己使用包括语句进一步定制。示例:您可以从特定的自定义include文件中在某些/所有站点上包含所需的额外SSL指令。您只需在需要时将该包含语句添加到您的所有虚拟站点中。|882421|更多(Debian/Ubuntu)：https://stackoverflow.com/a/11687212/503621|entityMap|0|LINK|mutability|MUTABLE|url|https://httpd.apache.org/docs/2.4/configuring.html#main|1|https://httpd.apache.org/docs/2.4/mod/core.html#include|2|https://stackoverflow.com/a/11687212/503621^0|0|0|0|1|13|0|2|K|N|L|0|D|A|O|C|0|4|7|0|0|0|1|14|0|2|K|N|L|0|4|7|0|0|0|A|0|0|C|2U|7|0|0|0|0|2C|7|8|D|0|1P|2|1|0|I|17|2^^$0|@$1|2|3|4|5|6|7|1R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1S|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1T|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|1U|8|@$I|1V|J|1W|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|1X|8|@$I|1Y|J|1Z|K|L]|$I|20|J|21|K|L]]|9|@]|A|$]]|$1|O|3|P|5|6|7|22|8|@$I|23|J|24|K|L]|$I|25|J|26|K|L]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|27|8|@$I|28|J|29|K|L]]|9|@]|A|$]]|$1|S|3|T|5|6|7|2A|8|@]|9|@]|A|$]]|$1|U|3|V|5|F|7|2B|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|2C|8|@$I|2D|J|2E|K|L]]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|2F|8|@$I|2G|J|2H|K|L]|$I|2I|J|2J|K|L]]|9|@]|A|$]]|$1|10|3|R|5|6|7|2K|8|@$I|2L|J|2M|K|L]]|9|@]|A|$]]|$1|11|3|12|5|6|7|2N|8|@]|9|@]|A|$]]|$1|13|3|14|5|6|7|2O|8|@$I|2P|J|2Q|K|L]]|9|@]|A|$]]|$1|15|3|16|5|6|7|2R|8|@$I|2S|J|2T|K|L]|$I|2U|J|2V|K|L]]|9|@]|A|$]]|$1|17|3|-4|5|6|7|2W|8|@]|9|@]|A|$]]|$1|18|3|19|5|6|7|2X|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|6|7|2Y|8|@]|9|@]|A|$]]|$1|1C|3|1D|5|6|7|2Z|8|@$I|30|J|31|K|L]]|9|@$I|32|J|33|1|34]|$I|35|J|36|1|37]]|A|$]]|$1|1E|3|1F|5|6|7|38|8|@]|9|@$I|39|J|3A|1|3B]]|A|$]]]|1G|$1H|$5|1I|1J|1K|A|$1L|1M]]|1N|$5|1I|1J|1K|A|$1L|1O]]|1P|$5|1I|1J|1K|A|$1L|1Q]]]]

Apache 2.4 (under Debian/Ubuntu)
For Configuration/Overrides (not necessarily a new site):
Place a new configuration file in <code>/etc/apache2/conf-available/{name}.conf</code>.
Enable/Disable your new config using <code>sudo a2enconf {name}</code>or <code>sudo a2disconf {name}</code>.
Directives in these can also override <code>httpd.conf</code> or <code>apache2.conf</code> as any additional config files added by user are read in last after main config.
Restart <code>apache2</code> service to reflect the change.
For Sites (and any site specific configuration overrides):
Place a new site file in <code>/etc/apache2/sites-available/{name}.conf</code>
Enable/Disable your site config using <code>sudo a2ensite {name}</code>or <code>sudo a2dissite {name}</code>.
Restart <code>apache2</code> service to reflect the change.
<hr />
Don't use:
<code>httpd.conf</code> is still installed as main config file on some Linux distributions. On others, you should NOT see it anymore - if you do, leave it empty as installed if you wish to upgrade Apache cleanly/easily via package manager.
<code>apache2.conf</code> is still installed on many systems and is used as the main configuration file for Debian/Ubuntu. But, leave it alone if you wish to upgrade Apache cleanly/easily. You should see some <code>include</code> statements near the bottom of this file for sites and custom configurations. 
Use them instead!
One, or both of these files may be installed via your Linux package manager depending on the Linux distribution. This is a good reason NOT to touch them since they could accidentally be overwritten during a system upgrade in the future.
Anything you might see in &quot;global&quot; <a href="https://httpd.apache.org/docs/2.4/configuring.html#main" rel="nofollow noreferrer">Apache2 configuration files</a> can be added/overridden under your custom config as per above. You can also use <a href="https://httpd.apache.org/docs/2.4/mod/core.html#include" rel="nofollow noreferrer">include</a> statements yourself to further customize. Example: You could include additional SSL directives you want on some/all sites from a specific custom <code>include</code> file. You would just add this include statement to all your virtual site configs as needed.
More (Debian/Ubuntu): <a href="https://stackoverflow.com/a/11687212/503621">https://stackoverflow.com/a/11687212/503621</a>

blocks|key|1918890|text|如果apache2.conf不是空的，而httpd.conf是空的，那么您可能应该使用apache2.conf+;-)|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1918891|但我认为其中一种包括另一种(其中一种完全是出于向后兼容性的原因而保留的)+--所以，它不应该有太大变化。|1918892|1918893|不过，如果您想添加一些内容，比如一个新的VirtualHost：难道没有另一个子目录可以将您的文件放在其中并包含它吗？|1918894|这可能是一个更好的解决方案:您不会修改默认文件--这将简化更新。|entityMap^0|2|C|K|A|17|C|0|0|0|K|B|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]|$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|V|8|@]|D|@]|E|$]]|$1|I|3|J|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|K|3|L|5|6|7|Z|8|@]|D|@]|E|$]]]|M|$]]

If <code>apache2.conf</code> is not empty, and <code>httpd.conf</code> is empty, you should probably use <code>apache2.conf</code> ;-)

But I suppose that one includes the other (and that one of those is kept purely for backward compatibility reasons) -- so, it shouldn't change much.

 
Still, if you want to add something, like a new <code>VirtualHost</code> : is there not another sub-directory, in which you could put your file, and have it included ?

It would probably be a better solution : you would not modify the default file -- which would simplify updates.

blocks|key|1919181|text|只需打开apache2.conf并查看内容：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1919182|Include+/etc/apache2/mod-enabled/*.conf
Include+/etc/apache2/httpd.conf|code-block|syntax|javascript|1919183|因此，如果您想包含您自己的配置，将其添加到httpd.conf中，那么apache2.conf将自动得到它。|1919184|正如其他人所说的，apache2.conf可以由机器生成，最好不要碰它。|1919185|有关更多信息，通常Ubuntu使用apache2.conf，Centos使用httpd.conf。因此，所有这些文件都取决于您拥有的操作系统。|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|O|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|P|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|Q|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|R|8|@]|9|@]|A|$]]]|M|$]]

just open apache2.conf and look at the content:

<pre><code>Include /etc/apache2/mod-enabled/*.conf
Include /etc/apache2/httpd.conf
</code></pre>

So if you want to include your own configuration add it to httpd.conf and apache2.conf will automatically get it.

As other say, apache2.conf can machine generated and it's better not to touch it.

For more information, generally Ubuntu uses apache2.conf and Centos uses httpd.conf. So all these files depends on which OS you have.

blocks|key|1919129|text|要查找配置文件的名称和位置，您必须：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1919130|1)在调用过程时进行搜索，在本例中使用apache用户：|1919131|ps+-ef+%7C+grep+apache|code-block|syntax|javascript|1919132|(在本例中，返回：httpd)|offset|length|style|CODE|1919133|2)显示二进制文件使用的变量：|1919134|httpd+-V+%7C+grep+'HTTPD_ROOT'+&&+httpd+-V+%7C+grep+'SERVER_CONFIG_FILE'|1919135|摘录和截图见：http://www.sysadmit.com/2016/12/linux-apache-donde-esta-httpdconf-apache2conf.html|entityMap|0|LINK|mutability|MUTABLE|url|http://www.sysadmit.com/2016/12/linux-apache-donde-esta-httpdconf-apache2conf.html^0|0|0|0|9|5|0|0|0|7|2A|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|12|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|13|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|14|8|@$K|15|L|16|M|N]]|9|@]|A|$]]|$1|O|3|P|5|6|7|17|8|@]|9|@]|A|$]]|$1|Q|3|R|5|F|7|18|8|@]|9|@]|A|$G|H]]|$1|S|3|T|5|6|7|19|8|@]|9|@$K|1A|L|1B|1|1C]]|A|$]]]|U|$V|$5|W|X|Y|A|$Z|10]]]]

To find the name and the location of the configuration file, you would have to:

1) Search as the process is called, in this case working with the apache user:

<pre><code>ps -ef | grep apache
</code></pre>

(in this example, returns: <code>httpd</code>)

2) Show the variables used by the binary:

<pre><code>httpd -V | grep 'HTTPD_ROOT' &amp;&amp; httpd -V | grep 'SERVER_CONFIG_FILE'
</code></pre>

Extracted and screenshots at: <a href="http://www.sysadmit.com/2016/12/linux-apache-donde-esta-httpdconf-apache2conf.html" rel="nofollow noreferrer">http://www.sysadmit.com/2016/12/linux-apache-donde-esta-httpdconf-apache2conf.html</a>

which one of these two files should I use to configure Apache?

The <code>httpd.conf</code> is empty, while <code>apache2.conf</code> is not.

It confuses me!

Ubuntu Apache: httpd.conf or apache2.conf?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我应该使用这两个文件中的哪一个来配置Apache？httpd.conf为空，而apache2.conf为空。把我弄糊涂了！

问Ubuntu : httpd.conf还是apache2.conf？
EN

回答 7

Server Fault用户

Server Fault用户

Server Fault用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Ubuntu : httpd.conf还是apache2.conf？EN

回答 7

Server Fault用户

Server Fault用户

Server Fault用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Ubuntu : httpd.conf还是apache2.conf？
EN