混合内容 jQuery ajax HTTPS 请求已在 Laravel 上被阻止
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/41865180/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
Mixed content jQuery ajax HTTPS request has been blocked on Laravel
提问by Ryan
I think this question will be easy for someone and will be a face-palm situation for me.
我认为这个问题对某人来说很容易，对我来说将是一个面对面的情况。
I have a Laravel 5.3 site, and various pages have ajax requests. Because I use the csrf_field()feature, they work fine.
我有一个 Laravel 5.3 站点，各种页面都有 ajax 请求。因为我使用了该csrf_field()功能，所以它们工作正常。
But there is one page where the ajax produces this error:
但是有一页 ajax 产生了这个错误：
Mixed Content: The page at 'https://example.com/fb/reports' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://example.com/fb/json?levelType=&id=&aggLevel=ad&start=&end='. This request has been blocked; the content must be served over HTTPS.
My javascript looks like this:
我的 javascript 看起来像这样：
var relUrl = '/fb/json/';
var payload = {
levelType: levelType,
id: id,
aggLevel: aggLevel,
start: start,
end: end
};
console.log(relUrl);
return $.ajax({
type: 'GET',
dataType: 'json',
data: payload,
url: relUrl,
headers: {
'X-CSRF-TOKEN': $('meta[name="csrf-token"]').attr('content')
}
});
I've read tonsof articles about this error. I've tried tons of suggested solutions, including changing the relative URL to the full https URL, or starting it with 2 slashes.
我已经阅读了大量有关此错误的文章。我已经尝试了大量建议的解决方案，包括将相对 URL 更改为完整的 https URL，或者以 2 个斜杠开头。
I've even tried changing the way my Laravel routes work and am now using just querystring parameters.
我什至尝试改变我的 Laravel 路由的工作方式，现在我只使用查询字符串参数。
I've studied all of the articles below (and more).
我已经研究了以下所有文章（以及更多文章）。
Also, since this one ajax query is in a password-protect part of the site (and the ajax queries that workare in a public/open part of the site), I figured maybe that was related to the problem. But then I used SSHto log into the production server and vimto temporarily remove the line that required any authentication, and the https error stillhappens.
此外，由于这一个AJAX查询是站点（和AJAX查询是一个有密码保护的部分工作是在网站的公共/开放的部分），我也许想通这是相关的问题。但是后来我曾经SSH登录生产服务器并vim临时删除需要任何身份验证的行，并且仍然发生https错误。
What steps can I take to debug further from here? What logs can I 'tail' on my Cloudways server?
我可以采取哪些步骤来进一步调试？我可以在 Cloudways 服务器上“拖尾”哪些日志？
Is there anything that Cloudflare might be interfering with (which I doubt, since other ajax queries work, all on https)?
Cloudflare 是否有任何可能会干扰的内容（我对此表示怀疑，因为其他 ajax 查询都在 https 上工作）？
Thanks!
谢谢！
- jQuery AJAX Request to HTTPS getting served to HTTP with Laravel and Select2
- This request has been blocked; the content must be served over HTTPS
- Mixed content issue - insecure XMLHttpRequest endpoint
- XHR response blocked by Chrome, because of mixed content issue (http/https)
- Forcing AJAX call to be HTTPS from HTTPS Page
- MixedContent when I'm loading https page through ajax, but browser still thinks it's http
- jQuery ajax won't make HTTPS requests
- Laravel 5.1 ajax url parameter is url
回答by Ryan
Summary:I needed to replace var relUrl = '/fb/json/';with var relUrl = '/fb/json';(remove the trailing slash) because that's what my Laravel web.phproutes file expected.
总结：我需要替换var relUrl = '/fb/json/';为var relUrl = '/fb/json';（删除尾部斜杠），因为这是我的 Laravelweb.php路由文件所期望的。
In Chrome console, I noticed that the httpsXHR request was being "canceled" and replaced with an httprequest.
在 Chrome 控制台中，我注意到httpsXHR 请求被“取消”并替换为一个http请求。
So then I used sshto log into the remote production server and vimto temporarily disable the requirement of authentication.
然后我曾经ssh登录到远程生产服务器并vim暂时禁用身份验证的要求。
Then in the Chrome console, I defined and ran a new ajax command using an absolute https URL with querystring params on the end. That worked (no mixed content error). Then I tried a relative URL like that, and it worked too.
然后在 Chrome 控制台中，我使用绝对 https URL 定义并运行了一个新的 ajax 命令，最后是查询字符串参数。那行得通（没有混合内容错误）。然后我尝试了一个这样的相对 URL，它也有效。
Even a relative URL with no payload or querystring params or trailing slash worked.
即使是没有有效负载或查询字符串参数或尾部斜杠的相对 URL 也能工作。
Then I added the trailing slash again, and it didn't work.
然后我再次添加了尾部斜杠，但它不起作用。
I still wish there had been an easier way to trace or debug the redirect paths or whatever was happening. I still feel like I stumbled onto the answer clumsily (after many hours) instead of knowing how to dissect this problem reliably.
我仍然希望有一种更简单的方法来跟踪或调试重定向路径或发生的任何事情。我仍然觉得我笨拙地（几个小时后）偶然发现了答案，而不是知道如何可靠地剖析这个问题。
