不使用HTTP身份验证的技术原因(Technical reasons to not use HTTP authentication)

不使用HTTP身份验证的技术原因(Technical reasons to not use HTTP authentication)

我发现HTTP支持一种身份验证系统来限制信息的可读性。 为什么大多数常见网站使用自己的系统 ，会话和许多东西来管理这种信息而不是HTTP身份验证？

I discovered that HTTP supports a system of authentication to restrict the readability of an information. Why do most common websites use their own system, with a session, and many stuff to manage this kind of information rather than HTTP authentication?

最满意答案

为什么大多数常见网站使用自己的系统，会话和许多东西来管理这种信息而不是HTTP身份验证？

如果有的话，那是因为http basic auth在询问凭证时会出现一个丑陋的阻塞模式窗口，其中，这使得无法自定义登录参数（例如，“记住我”/“这是公共计算机”复选框）。或验证码）。

Why do most common websites use their own system, with a session, and many stuff to manage this kind of information rather than HTTP authentication?

If anything, it's because http basic auth presents an ugly blocking modal window when asking for credentials, which, among other things, makes it impossible to customize login parameters ("remember me" / "this is a public computer" checkbox, for example. Or captcha).

不使用HTTP身份验证的技术原因(Technical reasons to not use HTTP authentication)

我发现HTTP支持一种身份验证系统来限制信息的可读性。 为什么大多数常见网站使用自己的系统 ，会话和许多东西来管理这种信息而不是HTTP身份验证？

I discovered that HTTP supports a system of authentication to restrict the readability of an information. Why do most common websites use their own system, with a session, and many stuff to manage this kind of information rather than HTTP authentication?

最满意答案

为什么大多数常见网站使用自己的系统，会话和许多东西来管理这种信息而不是HTTP身份验证？

如果有的话，那是因为http basic auth在询问凭证时会出现一个丑陋的阻塞模式窗口，其中，这使得无法自定义登录参数（例如，“记住我”/“这是公共计算机”复选框）。或验证码）。

Why do most common websites use their own system, with a session, and many stuff to manage this kind of information rather than HTTP authentication?

If anything, it's because http basic auth presents an ugly blocking modal window when asking for credentials, which, among other things, makes it impossible to customize login parameters ("remember me" / "this is a public computer" checkbox, for example. Or captcha).