blocks|key|393680|text|您可以将公共部分从两个服务器上下文移动到另一个配置文件和include。这应该是可行的：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|393681|server+{
++listen+80;
++server_name+server1.example;
++...
++include+/etc/nginx/include.d/your-common-stuff.conf;
}

server+{
++listen+80;
++server_name+another-one.example;
++...
++include+/etc/nginx/include.d/your-common-stuff.conf;
}|code-block|syntax|javascript|393682|编辑:这是一个示例，它实际上是从我正在运行的服务器复制的。我在/etc/nginx/sites-enabled中配置我的基本服务器设置(对于Ubuntu/Debian上的nginx来说是正常的东西)。例如，我的主服务器bunkus.org的配置文件是/etc/nginx/sites-enabled，它看起来像这样：|393683|server+{
++listen+++80+default_server;
++listen+++[2a01:4f8:120:3105::101:1]:80+default_server;

++include+/etc/nginx/include.d/all-common;
++include+/etc/nginx/include.d/bunkus.org-common;
++include+/etc/nginx/include.d/bunkus.org-80;
}

server+{
++listen+++443+default_server;
++listen+++[2a01:4f8:120:3105::101:1]:443+default_server;

++include+/etc/nginx/include.d/all-common;
++include+/etc/nginx/include.d/ssl-common;
++include+/etc/nginx/include.d/bunkus.org-common;
++include+/etc/nginx/include.d/bunkus.org-443;
}|393684|作为示例，下面是两个server上下文中包含的/etc/nginx/include.d/all-common文件：|393685|index+index.html+index.htm+index.php+.dirindex.php;
try_files+$uri+$uri/+=404;

location+~+/\.ht+{
++deny+all;
}

location+=+/favicon.ico+{
++log_not_found+off;
++access_log+off;
}

location+~+/(README%7CChangeLog)$+{
++types+{+}
++default_type+text/plain;
}|393686|entityMap^0|S|7|0|0|V|O|31|A|3H|O|0|0|A|6|N|V|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|Y|8|@$9|Z|A|10|B|C]|$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@]|E|$]]|$1|M|3|N|5|H|7|15|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|16|8|@$9|17|A|18|B|C]|$9|19|A|1A|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|H|7|1B|8|@]|D|@]|E|$I|J]]|$1|S|3|-4|5|6|7|1C|8|@]|D|@]|E|$]]]|T|$]]

You could move the common parts to another configuration file and <code>include</code> from both server contexts. This should work:

<pre><code>server {
 listen 80;
 server_name server1.example;
 ...
 include /etc/nginx/include.d/your-common-stuff.conf;
}

server {
 listen 80;
 server_name another-one.example;
 ...
 include /etc/nginx/include.d/your-common-stuff.conf;
}
</code></pre>

Edit: Here's an example that's actually copied from my running server. I configure my basic server settings in <code>/etc/nginx/sites-enabled</code> (normal stuff for nginx on Ubuntu/Debian). For example, my main server <code>bunkus.org</code>'s configuration file is <code>/etc/nginx/sites-enabled</code> and it looks like this:

<pre><code>server {
 listen 80 default_server;
 listen [2a01:4f8:120:3105::101:1]:80 default_server;

 include /etc/nginx/include.d/all-common;
 include /etc/nginx/include.d/bunkus.org-common;
 include /etc/nginx/include.d/bunkus.org-80;
}

server {
 listen 443 default_server;
 listen [2a01:4f8:120:3105::101:1]:443 default_server;

 include /etc/nginx/include.d/all-common;
 include /etc/nginx/include.d/ssl-common;
 include /etc/nginx/include.d/bunkus.org-common;
 include /etc/nginx/include.d/bunkus.org-443;
}
</code></pre>

As an example here's the <code>/etc/nginx/include.d/all-common</code> file that's included from both <code>server</code> contexts:

<pre><code>index index.html index.htm index.php .dirindex.php;
try_files $uri $uri/ =404;

location ~ /\.ht {
 deny all;
}

location = /favicon.ico {
 log_not_found off;
 access_log off;
}

location ~ /(README|ChangeLog)$ {
 types { }
 default_type text/plain;
}
</code></pre>

I have nginx acting as a reverse proxy to apache. I now need to add a new subdomain
that will serve files from another directory, but at the same time I want all location and proxy_pass directives that I have for the default host to apply to the subdomain also.

I know that if I copy the rules from the default host to the new subdomain it will work, but is there a way for the subdomain to inherit the rules?
Below is a sample configuration

<pre><code>server {
 listen 80;
 server_name www.somesite.com;
 access_log logs/access.log;
 error_log logs/error.log error;


 location /mvc {
 proxy_pass http://localhost:8080/mvc;
 }


 location /assets {
 alias /var/www/html/assets;
 expires max;
 }

 ... a lot more locations
}

server {
 listen 80;
 server_name subdomain.somesite.com;

 location / {
 root /var/www/some_dir;
 index index.html index.htm;
 }
}
</code></pre>

Thanks

Nginx subdomain configuration

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我让nginx充当apache的反向代理。我现在需要添加一个新的子域，它将为另一个目录中的文件提供服务，但同时我希望默认主机的所有location和proxy_pass指令也应用于该子域。我知道，如果我将规则从默认主机复制到新的子域，它将工作，但有没有办法让子域继承规则？下面是一个示例配置server {    lis...

Nginx子域配置-腾讯云开发者社区-腾讯云

问Nginx子域配置
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Nginx子域配置EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Nginx子域配置
EN