Azure CDN SSL HTTPS导致502错误的网关,但HTTP请求工作正常 [英] Azure CDN SSL HTTPS results in 502 Bad Gateway but HTTP requests work fine

查看:234
本文介绍了Azure CDN SSL HTTPS导致502错误的网关,但HTTP请求工作正常的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我最近刚刚在自定义域(Verizon Standard)上的Azure CDN上设置了https.如果重要的话,我正在通过cloudflare CNAME路由DNS.但是,无论我做什么,通过SSL访问Azure CDN都会得到502 Bad Gateway.

I've just recently setup https on Azure CDN on custom domains (Verizon Standard). I'm routing the DNS through cloudflare CNAME if that matters. However, no matter what I do, accessing Azure CDN over SSL I get a 502 Bad Gateway.

删除我的CNAME映射并直接访问,它仍然失败.是的,我可以直接通过SSL访问该文件.我的自定义Https显示已启用";在控制台中.

Removing my CNAME map and accessing directly, it still fails. And yes, I can access the file directly via SSL. My Custom Https shows "Enabled" in the console.

CDN Direct:

CDN Direct:

作品:http://barrysec.azureedge.net/wp-content/uploads/2017/01/3-1.jpg

Works: http://barrysec.azureedge.net/wp-content/uploads/2017/01/3-1.jpg

502:https://barrysec.azureedge.net/wp-content/uploads/2017/01/3-1.jpg

502: https://barrysec.azureedge.net/wp-content/uploads/2017/01/3-1.jpg

来源:

Works:http://www.seanbarry.com/wp-content/uploads/2017/01/3-1.jpg

Works: http://www.seanbarry.com/wp-content/uploads/2017/01/3-1.jpg

Works:https://www.seanbarry.com/wp-content/uploads/2017/01/3-1.jpg

Works: https://www.seanbarry.com/wp-content/uploads/2017/01/3-1.jpg

CNAME:

Works:http://cdn.seanbarry.com/wp-content/uploads/2017/01/3-1.jpg

Works: http://cdn.seanbarry.com/wp-content/uploads/2017/01/3-1.jpg

502:https://cdn.seanbarry.com/wp-content/uploads/2017/01/3-1.jpg

502: https://cdn.seanbarry.com/wp-content/uploads/2017/01/3-1.jpg

推荐答案

您可以验证是否在来源"(Origins)中选中了"HTTPS"您在Azure门户中的端点的选项卡"?

Can you verify that 'HTTPS' is checked in the "Origins" tab of your endpoint in the Azure portal?


这篇关于Azure CDN SSL HTTPS导致502错误的网关,但HTTP请求工作正常的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆