简体   繁体   English

“ Bearer”授权标头是否有特殊含义?

[英]Does the “Bearer” Authorization header have any special meaning?

Is there a difference between using a "Bearer" Authorization header and using a custom header? 使用“承载者”授权标头和使用自定义标头之间有区别吗? For example, the "Basic" Authorization header is different from a custom header because browsers treat "Basic" Authorization headers as a special case (some browsers cache the "Basic" Authorization header). 例如,“基本”授权标头与自定义标头不同,因为浏览器将“基本”授权标头视为特殊情况(某些浏览器会缓存“基本”授权标头)。 In other words, is "Bearer" just an arbitrary string or do browsers know about it? 换句话说,“承载者”是一个任意字符串还是浏览器知道吗?

If I don't want future browsers to cache my bearer token, should I be safe and use a custom header? 如果我不希望将来的浏览器缓存我的不记名令牌,是否应该安全并使用自定义标头?

For example, is there a difference between these (assuming my server can handle both): 例如,这两者之间有区别(假设我的服务器可以同时处理两者):

header('Authorization: Bearer 12345');
header('Mysite-Bearer-Token: 12345');

Bearer token is defined by OAuth 2.0. 承载令牌由OAuth 2.0定义。 You can get more details from http://tools.ietf.org/html/rfc6750 . 您可以从http://tools.ietf.org/html/rfc6750获得更多详细信息。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM