CKEditor 与 SCAYT over HTTPS 发出安全警告
我在 HTTPS/SSL 网页上有一个 CKEditor WYSIWYG 文本和 HTML 编辑器控件。我今天刚刚启用了 SCAYT（键入时进行拼写检查）功能，现在在页面加载时看到安全警告。
它似乎是由这四个文件引起的：
http://svc.spellchecker.net/spellcheck31/lf/scayt/_base.xd.jshttp://svc.spellchecker.net /spellcheck31/lf/scayt/nls/caption.xd.jshttp://svc.spellchecker.net/spellcheck31/lf/scayt/lang_list.jshttp:// /svc.spellchecker.net/spellcheck31/lf/scayt/resources/blank.gif
我发现了一个 此问题的票号#4065。据报道，SpellChecker.net 已于 12 天前纠正了该问题。
为什么我仍然在我的网站上看到警告？
说明
这些文件名没有出现在我的源代码中的任何位置。
I've got a CKEditor WYSIWYG text and HTML editor control on an HTTPS/SSL web page. I just today enabled the SCAYT (spell check as you type) feature and now see a Security Warning when the page loads.
It seems to be caused by these four files:
http://svc.spellchecker.net/spellcheck31/lf/scayt/_base.xd.jshttp://svc.spellchecker.net/spellcheck31/lf/scayt/nls/caption.xd.jshttp://svc.spellchecker.net/spellcheck31/lf/scayt/lang_list.jshttp://svc.spellchecker.net/spellcheck31/lf/scayt/resources/blank.gif
I found a Ticket #4065 for this issue. SpellChecker.net reportedly corrected the problem from their end 12 days ago.
Why do I still see the warning form my web site?
Clarification
Those file names don't appear anywhere in my source code.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
该问题已在 SpellChecker.net 端得到解决
The problem is resolved on SpellChecker.net side
可能是因为您仍在从 https 页面发出 http 请求 - 为什么会这样，我不知道，从 bug 来看，CKEditor 会自动切换协议。您没有对上面列出的这四个地址进行硬编码吗？
Probably because you are still making http requests from a https page - why that is, I don't know though, from the bug it looks like CKEditor will switch protocols automatically. You didn't hard-code those four addresses you list above?
您收到警告是因为脚本不是通过 ssl 链接 (https) 加载，而是通过常规 http 加载。
我尝试在浏览器中通过 ssl 手动获取第一个脚本，它似乎工作正常。
我对此组件没有任何直接经验，但我假设这些行是自动生成的。如果是这样，应该有一个设置来启用 ssl，或者应该由脚本自动检测。
如果您手动添加这些行，然后将 http:// 替换为 https://，那么它应该停止向您提供警告消息。
You are getting the warning because the scripts are not being loaded via a ssl link (https) just regular http.
I tried fetching the first script manually via ssl in my browser, and it seems to work fine.
I don't have any direct experience with this component, but I assume those lines were automatically generated. If so, there should be a setting somewhere to enable ssl, or it should be auto-detected by the script.
If you added the lines manually then replace the http:// wth https://, then it should stop giving you the warning message.