HTTPS 页面上带有 Backbone.js 的购物车有问题吗？
只是想知道使用 Backbone.js 构建购物车是否会出现任何问题，更具体地说，通过 HTTPS 使用 hash-bangs 是否存在任何安全问题？
另外我想我可以通过 AJAX 发布信用卡详细信息，对吗？
干杯，
just wondering if there could be any issue building a shopping cart using Backbone.js and more specifically if there were any security issues using hash-bangs over HTTPS?
Also I guess I can POST credit card details through AJAX, correct?
Cheers,
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您仍然需要 robots.txt 来防止您的网址被编入索引，即使您使用的是 HTTPS。与
#（散列）相反，#!（hashbang）提供了一种通过 url 片段对站点进行索引的方法。有关禁止的说明，请参阅有关为 hashbang 建立索引的 Google 页面。在实践中，您可能不必担心它，因为谷歌的爬虫没有经过身份验证，并且不会索引错误。但是，如果安装了 Google 工具栏，则在 Google 确定 URL+片段不会被索引之前，带有片段的 URL 可能会发送给 Google。为了简化操作，您可以在登录后使用#而不是#!；#深层链接不会被编入索引。如果请求是通过 HTTPS 发出的，则无论是否是 AJAX，都会对其进行加密。如果您的主干模型 url 以
https://开头，它将加密发送或失败。从网络窃听的角度来看，这与不使用 AJAX 进行发布是一样的。You still need robots.txt to keep your urls from being indexed, even if you're using HTTPS. The
#!(hashbang) as opposed to#(hash) provides a way to index sites by their url fragment. Instructions for disallowing are on the google page about indexing hashbang. In practice you likely won't have to worry about it because google's crawlers aren't authenticated and won't index an error. But if a Google Toolbar is installed the URLs with fragments may be sent to Google before Google determines that the URL+fragment will not be indexed. To simplify things, you could use#instead of#!after logging in; a#deep link will not be indexed.If a request is made through HTTPS, it's encrypted, whether it's AJAX or not. If your backbone model url starts with
https://, it will either send it encrypted or fail. From a network eavesdropping perspective, it's the same as posting without AJAX.