'刷新'HTTP标头 [英] 'Refresh' HTTP header

问题描述

我正在自动化一个Web应用程序（Mantis bug跟踪器），我从中获得一个有趣的响应标题，名为Refresh：

I'm automating a web application (the Mantis bug tracker) and I'm getting an interesting response header from it, called Refresh:

HTTP/1.x 200 OK
...
Refresh: 0;url=my_view_page.php

它似乎与元刷新确实如此，元刷新技术意味着它相当于HTTP中的标头。

It seems to be acting the same way that meta refresh does, and the meta refresh technique implies that it is an equivalent of a header in HTTP.

问题是，我找不到任何提及的刷新头 HTTP标准或有关如何解析它的任何其他权威文档浏览器遇到它时应该做什么。

Problem is, I can't find any mention of the Refresh header in the HTTP standard or any other definitive documentation on how it should be parsed and what the browser should do when it encounters it.

这里发生了什么？

推荐答案

据我所知，刷新（连同Set-Cookie和可能的其他专有伪标头）是由Netscap创建的在互联网的早期阶段，从那时起基本上（但不是很）标准。因为几乎每个浏览器都支持它，所以刷新使用起来非常安全 - 通常是。

As far as I know, Refresh (along with Set-Cookie and possibly some other proprietary pseudo-headers) were created by Netscape in the very early days of the internet and have been basically (but not quite) standard since then. Because just about every browser supports it, Refresh is pretty safe to use -- and commonly is.

我想它从未成为官方标准的一部分，因为它们已经有了规定使用状态代码。

I guess it never became part of the official standards because they already had provisions for that with the status codes.

这篇关于'刷新'HTTP标头的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！