什么是X-Forwarded-Proto HTTP标头的完整规范? [英] What is a full specification of X-Forwarded-Proto HTTP header?

查看:1113
本文介绍了什么是X-Forwarded-Proto HTTP标头的完整规范?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

什么是 X - 转发的Proto的 HTTP标头值?


解决方案<完整的规范/ div>

没有完整规范 - 它是事实上的标准。标题名称前面的 X - 通常是 * ,表示它是实验/非标准/供应商特定的。一旦它成为HTTP的标准部分,它就会丢失前缀。



IETF有一些标准化的工作,但它只是在草案阶段,到目前为止我可以告诉你。请查看 http://tools.ietf.org/html/draft截至撰写本文时,最新草稿的-ietf-appsawg-http-forwarded-10 。但请注意,它可以在它被充实的时候随时改变,并且在生产中不依赖它。



更新:



RFC 7239 现在定义转发:标头,用于替换 X-Forwarded - * 。如果您关心标准,我建议您使用它。






*这曾经是官方的事情,但不再是。 RFC 6648 不赞成的 X - 前缀约定。不幸的是,这个惯例是如此广为人知(并且这种低调的贬低),IETF以外的大多数人可能会忽略该建议。


What is a full specification of X-Forwarded-Proto HTTP header values?

解决方案

There is no "full specification" -- it's a de facto standard. The X- in front of a header name customarily* has denoted it as experimental/non-standard/vendor-specific. Once it's a standard part of HTTP, it'll lose the prefix.

There's some work from the IETF on standardizing it, but it's just at the draft stages, as far as i can tell. Check out http://tools.ietf.org/html/draft-ietf-appsawg-http-forwarded-10 for the latest draft as of the time of this writing. But be aware that it can change at any time while it's being fleshed out, and don't rely on it in production stuff yet.

Update:

RFC 7239 now defines the Forwarded: header, which is intended to replace X-Forwarded-*. If you care about standards, i would recommend using that instead.


* This used to be an official thing, but no longer is. RFC 6648 deprecates the X- prefixing convention. Unfortunately, the convention is so widely known (and the deprecation so low-key) that most people outside the IETF will probably ignore the recommendation.

这篇关于什么是X-Forwarded-Proto HTTP标头的完整规范?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆