基于nginx 动态 URL反向代理的实现

已于 2024-03-25 11:17:30 修改
阅读量562 收藏 4
点赞数 3
文章标签： nginx 大数据 运维
于 2024-03-25 11:15:53 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/daonidedie/article/details/136947853
版权

背景：

        我们在项目中在这样一个场景，用户需要使用固定的软件资源，这些资源是以服务器或者以容器形式存在的。

        资源以webAPI方式在内网向外提供接口，资源分类多种类型，每种类型的资源程序和Wapi参数都一样。这些资源部属完成后使用IP＋端口进行区分。如下表所示

     

技术分析：

经过调研分析，发现Nginx 可以进行么向代理，代理后可以进行调度到内部的数据

技术验证：

1.使用静态方式在配置文件中直接写入

如下：

server {
        listen        22280;
        server_name  localhost;
        root   "D:/dist";
        location / {
            index index.php index.html error/index.html;
            error_page 400 /error/400.html;
            error_page 403 /error/403.html;
            error_page 404 /error/404.html;
            error_page 500 /error/500.html;
            error_page 501 /error/501.html;
            error_page 502 /error/502.html;
            error_page 503 /error/503.html;
            error_page 504 /error/504.html;
            error_page 505 /error/505.html;
            error_page 506 /error/506.html;
            error_page 507 /error/507.html;
            error_page 509 /error/509.html;
            error_page 510 /error/510.html;
            #include D:/Git/111/nginx.htaccess;
            autoindex  off;
			try_files $uri $uri/ @router; #需要指向下面的@router否则会出现vue的路由在nginx中刷新出现404
			index  index.html index.htm;
        }
		#反向代理 
		location /r1/ {     
			proxy_pass http://192.168.1.88:888/;            
        }
				location /r2/ {     
			proxy_pass http://192.168.1.88:887/;            
        }
				location /i1/ {     
			proxy_pass http://192.168.1.89:3333/;            
        }
				location /i2/ {     
			proxy_pass http://192.168.1.90:3333/;            
        }
 
  #对应上面的@router，主要原因是路由的路径资源并不是一个真实的路径，所以无法找到具体的文件
  #因此需要rewrite到index.html中，然后交给路由在处理请求资源
		location @router {
				rewrite ^.*$ /index.html last;
			}
        location ~ \.php(.*)$ {
            fastcgi_pass   127.0.0.1:9000;
            fastcgi_index  index.php;
            fastcgi_split_path_info  ^((?U).+\.php)(/?.+)$;
            fastcgi_param  SCRIPT_FILENAME  $document_root$fastcgi_script_name;
            fastcgi_param  PATH_INFO  $fastcgi_path_info;
            fastcgi_param  PATH_TRANSLATED  $document_root$fastcgi_path_info;
            include        fastcgi_params;
        }
}

使用此方式可以达到所需效果，但如果资源变化需要手动调整Nginx的配置文件。因此考虑有没有一种办法可以做到动态转发呢？

问题难点：

1.资源需要一定的规律性

2.nginx动态转发功能技术上需要进行预研，明确是否可行

实现过程：

1.确定方案

方案里我们准备采用 固定内容+端口号的形式来进行处理，在此之前我们需要把服务用K8S映射到

同一IP或者同一规则的内容上。并且对URL进行了定义 /rs/(\d+)/实际API  的形式进行调用

2.方案实现

我们假定所有的 k8s 把所有的服务地址都映射到了 192.168.1.88上，仅端口不同，使用不同的端口就可以调度到不同的服务。

部分配置如下：

		location /rs/(\d.+)/ {     
			proxy_pass http://localhost:$/;            
        }

运行报错 http 500

500 Internal Server Error
nginx/1.15.11
问题处理：
2024/03/22 17:07:35 [error] 5072#34752: *264 rewrite or internal redirection cycle while redirect to named location "@router", client: 127.0.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", host: "127.0.0.1:280"
2024/03/22 17:07:35 [error] 5072#34752: *265 rewrite or internal redirection cycle while redirect to named location "@router", client: 127.0.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", host: "127.0.0.1:280"
2024/03/22 17:08:15 [error] 5072#34752: *268 rewrite or internal redirection cycle while redirect to named location "@router", client: 127.0.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", host: "127.0.0.1:280"
2024/03/22 17:08:16 [error] 5072#34752: *269 rewrite or internal redirection cycle while redirect to named location "@router", client: 127.0.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", host: "127.0.0.1:280"
2024/03/22 17:08:16 [error] 5072#34752: *270 rewrite or internal redirection cycle while redirect to named location "@router", client: 127.0.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", host: "127.0.0.1:280"
2024/03/22 17:08:17 [error] 5072#34752: *271 rewrite or internal redirection cycle while redirect to named location "@router", client: 127.0.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", host: "127.0.0.1:280"
2024/03/22 17:09:24 [error] 5072#34752: *273 rewrite or internal redirection cycle while redirect to named location "@router", client: 127.0.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", host: "127.0.0.1:280"
2024/03/22 17:09:24 [error] 5072#34752: *274 rewrite or internal redirection cycle while redirect to named location "@router", client: 127.0.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", host: "127.0.0.1:280"
2024/03/22 17:09:25 [error] 5072#34752: *275 rewrite or internal redirection cycle while redirect to named location "@router", client: 127.0.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", host: "127.0.0.1:280"
2024/03/22 17:09:26 [error] 5072#34752: *276 rewrite or internal redirection cycle while redirect to named location "@router", client: 127.0.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", host: "127.0.0.1:280"
2024/03/22 17:09:27 [error] 5072#34752: *277 rewrite or internal redirection cycle while redirect to named location "@router", client: 127.0.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", host: "127.0.0.1:280"
2024/03/22 17:09:27 [error] 5072#34752: *278 rewrite or internal redirection cycle while redirect to named location "@router", client: 127.0.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", host: "127.0.0.1:280"
2024/03/22 17:09:35 [error] 5072#34752: *283 rewrite or internal redirection cycle while redirect to named location "@router", client: 127.0.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", host: "127.0.0.1:280"
2024/03/22 17:09:36 [error] 5072#34752: *284 rewrite or internal redirection cycle while redirect to named location "@router", client: 127.0.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", host: "127.0.0.1:280"
2024/03/22 17:09:36 [error] 5072#34752: *285 rewrite or internal redirection cycle while redirect to named location "@router", client: 127.0.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", host: "127.0.0.1:280"
2024/03/22 17:09:37 [error] 5072#34752: *286 rewrite or internal redirection cycle while redirect to named location "@router", client: 127.0.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", host: "127.0.0.1:280"
2024/03/22 17:09:38 [error] 5072#34752: *287 rewrite or internal redirection cycle while redirect to named location "@router", client: 127.0.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", host: "127.0.0.1:280"
2024/03/22 17:09:38 [error] 5072#34752: *288 rewrite or internal redirection cycle while redirect to named location "@router", client: 127.0.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", host: "127.0.0.1:280"
2024/03/22 17:10:00 [error] 5072#34752: *279 upstream prematurely closed connection while reading response header from upstream, client: 127.0.0.1, server: localhost, request: "GET /uuu/60000/api/sysAuth/index.html HTTP/1.1", upstream: "http://192.168.27.51:60000/", host: "127.0.0.1:280"
2024/03/22 17:10:00 [error] 5072#34752: *279 rewrite or internal redirection cycle while processing "/index.html", client: 127.0.0.1, server: localhost, request: "GET /uuu/60000/api/sysAuth/index.html HTTP/1.1", upstream: "http://192.168.27.51:60000/", host: "127.0.0.1:280"
2024/03/22 17:10:01 [error] 5072#34752: *280 rewrite or internal redirection cycle while redirect to named location "@router", client: 127.0.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", host: "127.0.0.1:280", referrer: "http://127.0.0.1:280/uuu/60000/api/sysAuth/index.html"
2024/03/22 17:11:05 [error] 5072#34752: *290 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while reading response header from upstream, client: 127.0.0.1, server: localhost, request: "GET /uuu/60000/api/sysAuth/index.html HTTP/1.1", upstream: "http://192.168.27.51:60000/", host: "127.0.0.1:280"
2024/03/22 17:11:05 [error] 5072#34752: *290 rewrite or internal redirection cycle while processing "/index.html", client: 127.0.0.1, server: localhost, request: "GET /uuu/60000/api/sysAuth/index.html HTTP/1.1", upstream: "http://192.168.27.51:60000/", host: "127.0.0.1:280"
2024/03/22 17:11:05 [error] 5072#34752: *293 rewrite or internal redirection cycle while redirect to named location "@router", client: 127.0.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", host: "127.0.0.1:280", referrer: "http://127.0.0.1:280/uuu/60000/api/sysAuth/index.html"
2024/03/22 17:14:18 [error] 8748#17732: *1 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while reading response header from upstream, client: 127.0.0.1, server: localhost, request: "GET /uuu/60000/index.html HTTP/1.1", upstream: "http://192.168.27.51:60000/uuu/60000/index.html", host: "localhost:280"
2024/03/22 17:14:18 [error] 8748#17732: *1 rewrite or internal redirection cycle while processing "/index.html", client: 127.0.0.1, server: localhost, request: "GET /uuu/60000/index.html HTTP/1.1", upstream: "http://192.168.27.51:60000/uuu/60000/index.html", host: "localhost:280"
2024/03/22 17:14:19 [error] 8748#17732: *5 rewrite or internal redirection cycle while redirect to named location "@router", client: 127.0.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", host: "localhost:280", referrer: "http://localhost:280/uuu/60000/index.html"
2024/03/22 17:15:59 [error] 12116#31400: *4 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while reading response header from upstream, client: 127.0.0.1, server: localhost, request: "GET /uuu/60000/aaaa HTTP/1.1", upstream: "http://192.168.27.51:60000/", host: "localhost:280"
2024/03/22 17:15:59 [error] 12116#31400: *4 rewrite or internal redirection cycle while processing "/index.html", client: 127.0.0.1, server: localhost, request: "GET /uuu/60000/aaaa HTTP/1.1", upstream: "http://192.168.27.51:60000/", host: "localhost:280"
2024/03/22 17:15:59 [error] 12116#31400: *7 rewrite or internal redirection cycle while redirect to named location "@router", client: 127.0.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", host: "localhost:280", referrer: "http://localhost:280/uuu/60000/aaaa"
2024/03/22 17:20:20 [error] 33904#20644: *1 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while reading response header from upstream, client: 127.0.0.1, server: localhost, request: "GET /uuu/60000/api/sysAuth/captcha HTTP/1.1", upstream: "http://192.168.27.51:60000/", host: "localhost:280"
2024/03/22 17:20:20 [error] 33904#20644: *1 rewrite or internal redirection cycle while processing "/index.html", client: 127.0.0.1, server: localhost, request: "GET /uuu/60000/api/sysAuth/captcha HTTP/1.1", upstream: "http://192.168.27.51:60000/", host: "localhost:280"
2024/03/22 17:20:20 [error] 33904#20644: *4 rewrite or internal redirection cycle while redirect to named location "@router", client: 127.0.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", host: "localhost:280", referrer: "http://localhost:280/uuu/60000/api/sysAuth/captcha"
2024/03/22 17:24:31 [error] 41040#27804: *2 rewrite or internal redirection cycle while redirect to named location "@router", client: 127.0.0.1, server: localhost, request: "GET /favicon.ico HTTP/1.1", host: "localhost:280", referrer: "http://localhost:280/uuu/5257/api/sysAuth/captcha"
2024/03/22 17:24:35 [error] 41040#27804: *4 rewrite or internal redirection cycle while redirect to named location "@router", client: 127.0.0.1, server: localhost, request: "GET /_framework/aspnetcore-browser-refresh.js HTTP/1.1", host: "localhost:280", referrer: "http://localhost:280/uuu/5257/index.html"
2024/03/22 17:24:35 [error] 41040#27804: *11 rewrite or internal redirection cycle while redirect to named location "@router", client: 127.0.0.1, server: localhost, request: "GET /index-mini-profiler/includes.min.js?v=4.3.8+1120572909 HTTP/1.1", host: "localhost:280", referrer: "http://localhost:280/uuu/5257/index.html"
2024/03/22 17:24:35 [error] 41040#27804: *12 rewrite or internal redirection cycle while redirect to named location "@router", client: 127.0.0.1, server: localhost, request: "GET /_vs/browserLink HTTP/1.1", host: "localhost:280", referrer: "http://localhost:280/uuu/5257/index.html"
2024/03/22 17:24:35 [error] 41040#27804: *13 rewrite or internal redirection cycle while redirect to named location "@router", client: 127.0.0.1, server: localhost, request: "GET /swagger/%E5%85%AC%E5%85%B1%E6%9C%8D%E5%8A%A1/swagger.json HTTP/1.1", host: "localhost:280", referrer: "http://localhost:280/uuu/5257/index.html"
2024/03/22 17:35:40 [error] 41512#41416: *8 rewrite or internal redirection cycle while redirect to named location "@router", client: 127.0.0.1, server: localhost, request: "GET /_framework/aspnetcore-browser-refresh.js HTTP/1.1", host: "localhost:280", referrer: "http://localhost:280/area/5257/index.html"
2024/03/22 17:35:40 [error] 41512#41416: *10 rewrite or internal redirection cycle while redirect to named location "@router", client: 127.0.0.1, server: localhost, request: "GET /_vs/browserLink HTTP/1.1", host: "localhost:280", referrer: "http://localhost:280/area/5257/index.html"
2024/03/22 17:35:40 [error] 41512#41416: *9 rewrite or internal redirection cycle while redirect to named location "@router", client: 127.0.0.1, server: localhost, request: "GET /index-mini-profiler/includes.min.js?v=4.3.8+1120572909 HTTP/1.1", host: "localhost:280", referrer: "http://localhost:280/area/5257/index.html"
2024/03/22 17:35:40 [error] 41512#41416: *2 rewrite or internal redirection cycle while redirect to named location "@router", client: 127.0.0.1, server: localhost, request: "GET /swagger/%E5%85%AC%E5%85%B1%E6%9C%8D%E5%8A%A1/swagger.json HTTP/1.1", host: "localhost:280", referrer: "http://localhost:280/area/5257/index.html"

通过日志发现存在循环引用之类的

考虑使用URL重写改变下，路径。再使用proxy_pass反向代理。尝试修改nginx并进行修改。

问题解决
location ~ ^/rs/(\d.+)/{
			rewrite ^/rs/(\d+)/(.*)$ /$2 break;
			proxy_pass http://192.168.1.88:$1;  
        }

最终结果能够正常转发到指定端口，并且nginx 也不用修改配置，实现了动态端口反向代理。

在这个过程中我发现要实现/dir/port/xxx 这种进行反向代理必须与url重写结合使用。不然会报404.

完整能够成功运行的配置nginx.conf如下

server {
        listen        22280;
        server_name  localhost;
        root   "D:/dist";
        location / {
            index index.php index.html error/index.html;
            error_page 400 /error/400.html;
            error_page 403 /error/403.html;
            error_page 404 /error/404.html;
            error_page 500 /error/500.html;
            error_page 501 /error/501.html;
            error_page 502 /error/502.html;
            error_page 503 /error/503.html;
            error_page 504 /error/504.html;
            error_page 505 /error/505.html;
            error_page 506 /error/506.html;
            error_page 507 /error/507.html;
            error_page 509 /error/509.html;
            error_page 510 /error/510.html;
            #include D:/Git/111/nginx.htaccess;
            autoindex  off;
			try_files $uri $uri/ @router; #需要指向下面的@router否则会出现vue的路由在nginx中刷新出现404
			index  index.html index.htm;
        }
		#反向代理 
		location ~ ^/rs/(\d.+)/{
			rewrite ^/rs/(\d+)/(.*)$ /$2 break;
			proxy_pass http://192.168.1.88:$1;  
        }
 
  #对应上面的@router，主要原因是路由的路径资源并不是一个真实的路径，所以无法找到具体的文件
  #因此需要rewrite到index.html中，然后交给路由在处理请求资源
		location @router {
				rewrite ^.*$ /index.html last;
			}
        location ~ \.php(.*)$ {
            fastcgi_pass   127.0.0.1:9000;
            fastcgi_index  index.php;
            fastcgi_split_path_info  ^((?U).+\.php)(/?.+)$;
            fastcgi_param  SCRIPT_FILENAME  $document_root$fastcgi_script_name;
            fastcgi_param  PATH_INFO  $fastcgi_path_info;
            fastcgi_param  PATH_TRANSLATED  $document_root$fastcgi_path_info;
            include        fastcgi_params;
        }
}

生财
关注
  • 3
    点赞
  • 踩
  • 4
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
基于Nginx 反向代理获取真实IP的问题详解
01-10
一、前言 前文Nginx 解决WebApi跨域二次请求以及Vue单页面问题 当中虽然解决了跨域问题带来的二次请求，但也产生了一个新的问题，就是如果需要获取用户IP的时候，获取的IP地址总是本机地址。 二、原因 由于Nginx反向代理后，在应用中取得的IP都是反向代理服务器的IP，取得的域名也是反向代理配置的Url的域名。 三、解决方案 解决该问题，需要在Nginx反向代理配置中添加一些配置信息，目的将客户端的真实IP和域名传递到应用程序中。同时，也要修改获取IP地址的方法。 但是需要注意的是，通过Nginx反向代理后，如果访问IP通过了几层代理，可能取得的IP地址是这种格式：clientIP,
Nginx 动态反向代理
qq_36522188的博客
08-04 1379
request_filename 当前请求的文件路径名，比如/opt/nginx/www/test.php。$server_protocol 请求的协议版本，“HTTP/1.0"或"HTTP/1.1”$host 请求信息中的"Host"，如果请求中没有Host行，则等于设置的服务器名。$request_method 请求的方法，比如"GET"、"POST"等。$content_type 请求信息里的"Content-Type"$uri 请求的URI，可能和最初的值有不同，比如经过重定向之类的。...
Nginx转发到动态域名的proxy.conf
04-23
Nginx在vhost里的配置站点，通过proxy转发到动态域名的具体配置。 反向代理，动态域名 ，Proxy
基于带有API的NGINX OpenResty的动态反向代理-Python开发
05-25
Ceryx-坚固，可编程的HTTP（S）反向代理Ceryx是坚固，可编程的反向代理，用于为成千上万的SourceLair项目提供其独特的，启用HTTPS的公共URL。 High-le Ceryx-坚固，可编程的HTTP（S）反向代理Ceryx是坚固，可编程的反向代理，用于为成千上万的SourceLair项目提供其独特的，启用HTTPS的公共URL。 高层体系结构使Ceryx坚如磐石的主要特征之一就是其设计的简洁性。 Ceryx由两个组件和一个Redis后端组成：HTTP（S）反向代理和一个API。 代理Ceryx在后台使用NGINX OpenResty路由请求，基于
ceryx, 基于API的Nginx OpenResty动态反向代理.zip
09-18
ceryx, 基于API的Nginx OpenResty动态反向代理 Ceryx - 简单，但功能强大的反向代理 Ceryx是一种基于 Nginx OpenResty的动态反向代理。Ceryx用于在 https://www.sourcelair.com 为数万个项目提供 public url 。代
Nginx反向代理 URL【参数】转换为URL 【Path】，支持Post请求
热门推荐
wjxcai的博客
03-05 1万+
Nginx反向代理 URL【参数】转换为URL 【Path】，支持Post请求, 如访问路径为 http://www.domain.com/abc/efg/key=xxx， 反向代理为 http://192.168.0.113:8000/xxx/abc/efg/key=xxx
Nginx 根据url参数设置反向代理
youngtong的博客
11-23 6521
部署Nginx nginx 部署依赖的其他包⾃⾏下载安装，本次试验的是 1.6.2 版本。下载 nginx 安装包： wget http://nginx.org/download/nginx-1.6.2.tar.gz 编译安装 # ./configure # make # make install 启动 Nginx /usr/local/nginx/sbin/nginx 配置nginx nginx 配置⽂件路径⼀般为 /usr/local/nginx/conf，修改 ngin...
Nginx-反向代理配置学习总结
DM的个人练习
01-29 3186
nginx反向代理配置学习总结
【Nginx】反向代理 跨域处理 带参转发
ranmaxli的博客
08-27 1190
conf 代码 location /showImg{ proxy_pass http://192.168.0.219:9012/showImg; } 说明 /showImg： 项目原目录层级 http://192.168.0.219:9012/showImg; 跳转到的服务地址加上目录层级 这里也不需要写正则，转发请求时会自动将后面的参数带上。 ...
一次说清-Nginx反向代理及参数配置
m0_71777195的博客
05-30 3431
我们在配置服务时常常会用到Nginx来设置反向代理，虽然常用，但是我们真的了解各个参数的意思吗？不如我们一起来看下吧。
ceryx：基于NGINX OpenResty和API的动态反向代理
02-02
Ceryx-坚固，可编程的HTTP（S）反向代理 Ceryx是坚如磐石的可编程反向代理，用于为成千上万的项目提供其独特的，启用HTTPS的公共URL。 高层架构 Ceryx坚如磐石的主要特征之一就是其设计的简洁性。 Ceryx由两个组件和一个Redis后端组成：HTTP（S）反向代理和一个API。 代理 Ceryx在后台使用NGINX OpenResty来路由请求，该请求基于HTTP请求的Host标头或HTTPS请求中的。 Ceryx查询Redis后端，以确定它将每个请求路由到哪个目标。 API Ceryx API使用户可以通过任何HTTP客户端动态创建，更新和删除Ceryx路由。 该API本质上是验证，清除并最终将输入存储在Ceryx后端中，以供代理查询。 组态 Ceryx配置有以下环境变量： CERYX_API_HOST ：绑定Ceryx API的主机（默认值： 127.0.0.1 ） CERYX_API_HOSTNAME ：Ceryx API的可选公共可访问主机名（默认：无） CERYX_API_PORT ：绑定Ceryx API的端口（默认值： 5555 ） CER
Nginx+lua通过url传参的方式实现动态代理
07-20
需求大致如下:通过url传参的方式,让Nginx代理到不同的服务器 浏览器输入:http://127.0.0.1/remote?port=8081被代理到:http://192.168.108.2:8081
php-Reverse-Proxy:反向代理
04-23
镜像站点，并输出，用于替代nginx的反向代理 已经实现 v1 全站的反代 v1 header跟随跳转 v1 cookies的基本适配 计划中 缓存的建立更新、删除 cookies和session的同步等功能的实现 ip地址的穿透 简单的字符串替换等 ...
ELK日志系统的搭建
adminstate的博客
04-23 1041
ELK日志系统搭建
【Hadoop】-HDFS的存储原理[4]
weixin_63106307的博客
04-20 1422
HDFS的存储原理是将大文件切分成固定大小的数据块，并在集群中的不同节点上存储数据块的，以提高数据的可靠性和性能。同时，HDFS采用流式的数据读写方式，减少了寻址的开销，提高了数据的传输效率。
ElasticSearch 入门学习
最新发布
灰熊
04-23 758
ElasticsSearch 是一个分布式的实时文档存储，每个字段可以被索引与搜索也是一个分布式实时分析搜索引擎也是一个能胜任上百个服务节点的扩展，并支持 PB 级别的结构化或者非结构化数据。
深入理解Java消息中间件-RabbitMQ
u011532237的博客
04-21 828
RabbitMQ是基于高级消息队列协议（AMQP）实现的一款开源消息代理软件，旨在提供高可用性、安全、互操作性强的企业消息系统。它由Erlang编写，因而继承了Erlang语言高并发、高可靠性的特点。
大数据——Zookeeper ZBA协议（四）
大数据爱好者的博客
04-20 893
对于分布式框架而言，基本上都会遵循CAP三大理论CAP(CAP理论是从客户端角度出发的！！！C(Consistency)：一致性。在一段时间内，访问这个集群获取到的数据是相同的。注意，此时，在一个时间段内，不要求每一台服务器的数据都一样，只要保证客户端获取到的数据一样就行A(Availability)：可用性。当客户端对集群中的节点发起请求的时候，节点能够在合理的时间内(一般理解为立刻)进行响应 - 时效性。注意，此处的可用性和服务器的高可用不是一回事儿！！！
nginx四层和七层代理
09-14
Nginx可以作为四层和七层代理。四层代理是基于IP和端口的转发，通过TCP/UDP协议进行通信。Nginx从1.9.0版本开始支持四层代理，需要在编译时添加--with-stream模块。四层代理主要用于负载均衡，根据报文中的目标地址和端口以及负载均衡设备的设置来选择内部服务器。例如，可以创建ssh、mysql等业务集群。 七层代理是基于应用层的转发，可以处理HTTP请求。Nginx一般支持七层代理，它可以代理客户端访问服务端。七层代理的特点是可以根据报文内容进行更精确的转发决策，例如根据URL、域名等信息进行转发。七层代理可以用于反向代理web服务器，常用于负载均衡和高可用性方案。 四层代理和七层代理的配置上有一些差异。七层代理在proxy_pass配置行上需要添加http://集群名，而四层代理不需要。另外，四层代理和七层代理都可以用于反向代理，但七层代理还可以用作正向代理。所以，Nginx的四层和七层代理有一些区别，但它们都是Nginx在不同层级上进行代理转发的方式。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值