We don’t allow questions seeking recommendations for software libraries, tutorials, tools, books, or other off-site resources. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
接受
或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论(2)
我认为 HTTP 连接的短 URL 确实是个坏主意。 毕竟,SSL 的作用是确保(其工作的一部分)您实际上正在与所请求的服务器进行通信。
但在短 URL 场景中,您首先与不同的服务器通信 - 这是理想的诈骗情况。
I think short URLs for HTTPs connections are really bad idea. After all SSL is here to ensure (part of its job) that you are actually talking to the server requested.
But in short URL scenario you are talking to a different server first - an ideal scammer situation.
Bit.ly 不要求您使用其 API 发送密码; 它们要求您传递一个与您的密码没有任何关系的令牌(也称为 API 密钥)。 毕竟这是一个 URL 缩短服务。 无论如何,考虑到所有信息几乎都是公开的,安全性不应该成为问题。
Bit.ly doesn't require you to send a password using their API; they require you to pass a token (aka API Key) that isn't in any way tied to your password. It's an URL shortening service after all. Considering all the information is pretty much public anyway, security shouldn't be a concern.