浏览器对电子标签的支持

发布于 2024-11-14 03:10:36 字数 124 浏览 3 评论 0原文

我正在努力让我的网站支持 eTag/If-None-Match 浏览器缓存,但我不确定哪些浏览器支持/不支持它。谁能指点我一份清单吗?我无法想象它是普遍的,但我还没有找到任何支持这种说法的东西。

干杯,
麦克风

I'm working on getting my site to support the eTag/If-None-Match browser cache, but I'm not sure which browsers do/don't support it. Can anyone point me to a list? I can't imagine it's universal, but I haven't found anything that supports that claim.

cheers,
Mike

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

瘫痪情歌 2024-11-21 03:10:36

HTTP 1.1(1999 年 6 月)中指定了 If-None-Match:

根据维基百科:

到 1996 年 3 月,Arena、Netscape 2.0、Netscape Navigator Gold 2.01、Mosaic 2.7、Lynx 2.5 和 Internet Explorer 3.0 都支持预标准 HTTP/1.1。最终用户很快就采用了新浏览器。 1996 年 3 月,一家网络托管公司报告称,互联网上使用的浏览器中有超过 40% 符合 HTTP 1.1 标准。该网络托管公司报告称,到 1996 年 6 月,访问其服务器的所有浏览器中有 65% 符合 HTTP/1.1 标准。 RFC 2068 中定义的 HTTP/1.1 标准于 1997 年 1 月正式发布。HTTP/1.1 标准的改进和更新于 1999 年 6 月在 RFC 2616 下发布。

根据我的经验,所有流行的浏览器,IE5.5+, Safari、Chrome、Opera 和 Firefox 都支持 ETag/If-None-Match 标头。

但是,还有一些其他标头会阻止这些浏览器尊重 etag...因此,如果它不适合您,我会仔细检查当客户端请求资源时发送回客户端的其他标头。

您问这个问题有什么特别的理由吗?也许如果您有一个特定的实例遇到问题,我们可以查看其他标头?

但这些标头已经存在很长时间了,它们是网络上广泛使用的关键缓存机制。

If-None-Match was Specified in HTTP 1.1 (June 1999):

According to Wikipedia:

By March 1996, pre-standard HTTP/1.1 was supported in Arena, Netscape 2.0, Netscape Navigator Gold 2.01, Mosaic 2.7, Lynx 2.5, and in Internet Explorer 3.0. End user adoption of the new browsers was rapid. In March 1996, one web hosting company reported that over 40% of browsers in use on the Internet were HTTP 1.1 compliant. That same web hosting company reported that by June 1996, 65% of all browsers accessing their servers were HTTP/1.1 compliant. The HTTP/1.1 standard as defined in RFC 2068 was officially released in January 1997. Improvements and updates to the HTTP/1.1 standard were released under RFC 2616 in June 1999.

In my experience, all browsers in popular use, IE5.5+, Safari, Chrome, Opera, and Firefox, all support the ETag/If-None-Match headers.

However, there are some other headers which will stop these browsers from respecting the etag... so if it's not working for you, I'd carefully examine the other headers being sent back to the client when they request a resource.

Do you have any particular reason for asking the question? Maybe if you had a specific instance you were having an issue with, we could look at the other headers?

But these headers have been around for a long time, and they are a key caching mechanism used widely around the net.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文