nginx

Websocket Cloudflare with Nginx 520 error

由 我是研究僧i 提交于 2021-01-07 02:13:56
问题 I am jumping in on a project with some socket issues over SSL and Cloudflare... I know.. I have read about 50 different stack overflow posts and 200 blog posts to try to figure this out. The project works on my local dev server/computer just fine... I think I am on the right track - But could use some help/pointers if ya'll can. First, I thought it was weird that the /socket-io/ proxy_pass was at port 6379, the same as redis... Maybe it should be? When this was set at 6379, the socket

Websocket Cloudflare with Nginx 520 error

由 一曲冷凌霜 提交于 2021-01-07 02:10:23
问题 I am jumping in on a project with some socket issues over SSL and Cloudflare... I know.. I have read about 50 different stack overflow posts and 200 blog posts to try to figure this out. The project works on my local dev server/computer just fine... I think I am on the right track - But could use some help/pointers if ya'll can. First, I thought it was weird that the /socket-io/ proxy_pass was at port 6379, the same as redis... Maybe it should be? When this was set at 6379, the socket

Websocket Cloudflare with Nginx 520 error

由 孤人 提交于 2021-01-07 02:10:13
问题 I am jumping in on a project with some socket issues over SSL and Cloudflare... I know.. I have read about 50 different stack overflow posts and 200 blog posts to try to figure this out. The project works on my local dev server/computer just fine... I think I am on the right track - But could use some help/pointers if ya'll can. First, I thought it was weird that the /socket-io/ proxy_pass was at port 6379, the same as redis... Maybe it should be? When this was set at 6379, the socket

Websocket Cloudflare with Nginx 520 error

由 五迷三道 提交于 2021-01-07 02:08:28
问题 I am jumping in on a project with some socket issues over SSL and Cloudflare... I know.. I have read about 50 different stack overflow posts and 200 blog posts to try to figure this out. The project works on my local dev server/computer just fine... I think I am on the right track - But could use some help/pointers if ya'll can. First, I thought it was weird that the /socket-io/ proxy_pass was at port 6379, the same as redis... Maybe it should be? When this was set at 6379, the socket

Two Flask apps on different paths with Kubernetes Ingress resource (nginx)

由 半世苍凉 提交于 2021-01-07 01:32:53
问题 My goal is the following: I have two Flask apps in two separate Docker containers and I want to access them via different paths on the same IP address, like this: 127.0.0.1/app1, 127.0.0.1/app2 (but with a real IP address). I want to do this with Kubernetes. I have a Kubernetes cluster running (Azure Kubernetes Service), with a Deployment and Service for each of the two Docker containers. The pod for each app is running fine. I also installed an ingress controller (Nginx) in my cluster and

Using self-signed certificates in nginx Ingress

由 徘徊边缘 提交于 2021-01-07 01:30:43
问题 I'm migrating services into a kubernetes cluster on minikube, these services require a self-signed certificate on load, accessing the service via NodePort works perfectly and demands the certificate in the browser (picture below), but accessing via the ingress host (the domain is modified locally in /etc/hosts) provides me with a Kubernetes Ingress Controller Fake Certificate by Acme and skips my self-signed cert without any message. The SSLs should be decrypted inside the app and not in the

Using self-signed certificates in nginx Ingress

由 家住魔仙堡 提交于 2021-01-07 01:24:06
问题 I'm migrating services into a kubernetes cluster on minikube, these services require a self-signed certificate on load, accessing the service via NodePort works perfectly and demands the certificate in the browser (picture below), but accessing via the ingress host (the domain is modified locally in /etc/hosts) provides me with a Kubernetes Ingress Controller Fake Certificate by Acme and skips my self-signed cert without any message. The SSLs should be decrypted inside the app and not in the

还不升级http/2就跟不上时代了

由 家住魔仙堡 提交于 2021-01-07 00:54:40
http/2起飞 第一次听到http/2这个词，是在一些技术社区里大佬闲暇谈资时提起的，当时以为是不是啥类似protobuf协议的东西，后来了解后发现是我想偏了😄。 http/2从字面上看也是和http协议相关的，只是http/1的升级版。http/2协议标准于2015年正式发布，该标准协议有Chrome, Opera, Firefox, Safari, Edge等主流大厂共同制定， 所以http/2的市场支持是相当可以的。截至2019年6月，全球有36.5%的网站都支持了http/2。为此还下了个chrome检测http/2的扩展，打开网站只要是支持了http/2这个小插件就亮了。 不装不知道，一装发现很多国内网站都支持了http/2。 那么这么多网站都支持，我也要尝试下了，不然感觉就不时髦了。 由于我的大部分服务器都是采用的nginx，这里就说一下通过nginx升级到http/2。 首先nginx支持http/2的话最低配需要的是1.10.0和openssl的1.0.2版本，同时http/2在实现上只支持https。 也就是说你想http/2起飞的话，需要满足三个条件， 1.nginx版本大于等于1.10.0 2.openssl版本大于等于1.0.2 3.需要支持https，有https证书 我有https证书，这点满足了，然后是我 nginx -V

字节跳动着么缺人？不卡学历，不卡经验，只要求...

由 て烟熏妆下的殇ゞ 提交于 2021-01-06 21:19:58
由于国内用户对电商购物的热衷，再加上这些年，商家推出的各种优惠补贴策略和高效快捷的物流，也让大家足不出门享受到了真正的实惠。 但，对于一个 java 程序员 来讲，我更关注的是 系统架构层面 ，从原本的定时秒杀，到现在的各种 活动预热、拼团、定金膨胀、百亿补贴、跨店满减、以及更复杂的组合优惠 ，让用户一时摸不到头脑，虽然扰乱了用户购买的节奏，但也一直保持着持续升温的状态。 那么从 技术层面来分析 的话，这次优惠的复杂程度会造成原本就会有的 集中式秒杀 ，变成了 持续式高并发请求 ，这让我们的技术架构更为复杂，尤其是对 后台系统 而言， 复杂的链路调用 ，更多缓存逻辑和业务叠加给程序员们增加了额外的挑战。 当然像淘宝、京东、拼多多这种体量的用户群，在双十一之前早就做好了应对方案 对于在做 二三线电商 的小伙伴或想要了解淘宝、京东内部架构的小伙伴，我总结了以下几点技术总结： 技术总结： 电商高并发系统架构，SpringCloud Alibaba是如何应对双十一 抗住淘宝双十一的三大利器：Sentinel、Nacos、RocketMQ Sentinel在淘宝双十一洪峰时限流底层实现原理 Alibaba Sentinel对比 Netflix Hystrix区别与优势 Nacos在淘宝中如何抗住百万服务注册发现与配置下发 RocketMQ在双十一秒杀时如何抗住亿级订单数据

OpenYurt 入门

由 。_饼干妹妹 提交于 2021-01-06 18:15:19
： 你填了吗？ 10人将获赠CNCF商店$100美元礼券！ 来参与2020年CNCF中国云原生调查 问卷链接（ https://www.wjx.cn/jq/97146486.aspx ） 作者 | 唐炳昌 随着边缘计算的快速发展，越来越多的数据需要到网络的边缘侧进行存储、处理和分析，边缘的设备和应用呈爆发式增长。如何高效的管理边缘侧的资源和应用是业界面临的一个主要问题。当前，采用云原生的方法，将云计算的能力下沉到边缘并在云端做统一调度、管控的云边端一体化架构得到了业界的广泛认可。 2020 年 5 月，阿里巴巴开源首个 Kubernetes 无侵入的边缘计算云原生项目 OpenYurt ，并于同年 9 月份进入 CNCF SandBox。OpenYurt 针对边缘场景中网络不稳定、云边运维困难等问题，对原生 Kubernetes 无侵入地增强，重点提供了边缘节点自治、云边运维通道、边缘单元化的能力。 如图 1 所示，本文通过在云端部署 Kubernetes 集群的控制面，并将树莓派接入集群来搭建云管边场景。基于这个环境演示 OpenYurt 的核心能力，带大家快速上手 OpenYurt。 图 1 原生 Kubernetes 集群 环境准备 1. 基础环境介绍 在云端，购买 ENS 节点（ENS 节点具有公网 IP，方便通过公网对外暴露服务）来部署原生 K8s 集群的管控组件
订阅 nginx