nginx 已有80端口服务如何在开启一个非80端口的静态资源指向

最新推荐文章于 2023-09-07 17:34:36 发布

琅琊山二当家

最新推荐文章于 2023-09-07 17:34:36 发布

阅读量5k

点赞数

分类专栏： nginx

本文链接：https://blog.csdn.net/AlbertFly/article/details/52814024

版权

nginx 专栏收录该内容

15 篇文章 0 订阅

订阅专栏

要求是这样的当前以及有一个80端口 http服务的的动态server A 然后A服务也有也有静态资源的指向

如果这个时候在这这个nginx做一个新的非80服务的纯静态资源包的指向如何做？

1 首先给出一个例子针对的不是上面描述的需求就是已经有一个非80端口的静态资源指向，再给出另外一个别的非80端口的静态资源的指向

server {
	listen 7080 default_server;
	#listen [::]:80 default_server ipv6only=on;

	add_header Access-Control-Allow-Origin '*' ; #X-UA-Compatible 'IE=Edge,chrome=1'
	
	error_page 400 403 404 /error_pages/404.html;
	root /usr/share/nginx/html;
	index index.html index.htm;

	# Make site accessible from http://localhost/
	server_name localhost;

	location / {
		# First attempt to serve request as file, then
		# as directory, then fall back to displaying a 404.
		try_files $uri $uri/ =404;
		# Uncomment to enable naxsi on this location
		# include /etc/nginx/naxsi.rules
	}
	
	location ~ ^/nginx_status/ {
	    stub_status on;
	    access_log off; 
	}
	

server {
	listen 9810 default_server;
	#listen [::]:80 default_server ipv6only=on;

	error_page 400 403 404 /error_pages/404.html;
	root /Revit;
	index index.html index.htm;

	# Make site accessible from http://localhost/
	server_name localhost;

	location / {
		# First attempt to serve request as file, then
		# as directory, then fall back to displaying a 404.
		try_files $uri $uri/ =404;
		# Uncomment to enable naxsi on this location
		# include /etc/nginx/naxsi.rules
	}
}


server {
	listen 9991 default_server;
	#listen [::]:80 default_server ipv6only=on;

	error_page 400 403 404 /error_pages/404.html;
	root /var/www/html;
	index index.html index.htm;

	# Make site accessible from http://localhost/
	server_name localhost;

	# location ~ /seaf {
		# First attempt to serve request as file, then
		# as directory, then fall back to displaying a 404.
	# 	try_files $uri $uri/ =404;
		# Uncomment to enable naxsi on this location<pre name="code" class="html"><span style="font-family: Arial, Helvetica, sans-serif;">		# include /etc/nginx/naxsi.rules</span>

# }}

上例中就是7080端口做一个静态指向，然后9991 也是一个新的静态资源指向 root指向对应的静态资源

2 下面给出本文开始说的那种情况的一个解决思路

当前已经有针对80服务的端口的nginx的代理服务，如果再加一个静态资源包的指向

使用上面添加9991端口的方法就不行了测试发现会被80端口服务拦截

经过尝试发现一个折中的办法

在80代理的server 首先指向静态资源包的文件夹名字所有带有该文件夹名字的url 会被拦截然后就不走后面的80的端口代理了

如下

server {
    listen       80 default;
    server_name  _;
	index index.html index.htm index.jsp;
	root html;
		
	location ^~ /xxxxxxfmTemp/ {
            root /nodejs/;   ##会指向/home/admin/www  
            autoindex on;       ##会自动显示资源目录  
          # index noindex.htm;        
         }
	

	location ~ /XXXXXapp
	{
		proxy_pass    http://127.0.0.1:8080;
	}
	
	

	location ~ .*\.(gif|jpg|jpeg|png|bmp|swf)$
	{
		
		expires 30d;
	}

	location ~ .*\.(js|css)?$
	{
 		
		expires 1h;
	}

	access_log  /usr/local/nginx/logs/access.log;
}

静态资源的调用

http://120.xxx.xxx.231/xxxxxxfmTemp/admin/zjzx_index.html