Google搜索何时开始发送X-Frame-Options：SAMEORIGIN？ [英] When did Google Search start sending X-Frame-Options: SAMEORIGIN?

问题描述

我的应用程序已经进行了自动化测试，其中包括在IFrame中显示Google搜索框。最近，当开发人员检查了一个破坏了其他几项测试的变更时，测试开始失败。我开始怀疑这次改变打破了这个考验，但我很想知道。截至目前，我可以看到Google搜索（ ie ， http： //www.google.com/search?q=whatever ）使用 SAMEORIGIN X-Frame-Options 标头c $ c>，告诉浏览器不要在我们的IFrame中显示搜索页面。这是谷歌坚持的权利，我不介意。但是为了帮助我弄清楚测试失败是否是开发人员代码更改的错误或仅仅是巧合，我想知道 Google何时开始发送此X-Frame-Options标头？如果它碰巧在正确的时间附近，我们只是改变测试以做更合适的事情。

I've got an automated test for our application that includes displaying a Google search box in an IFrame. The test started failing recently, when a developer checked in a change that broke several other tests. I'm starting to doubt that the change broke this test, but I'd love to know for sure. As of right now, I can see that Google search (i.e., http://www.google.com/search?q=whatever) returns an X-Frame-Options header with SAMEORIGIN, which tells the browser not to display the search page in our IFrame. Which is Google's right to insist on, and I don't mind that. But to help me figure out if the test failure is the fault of the developer's code change or simply a coincidence, I'd love to know when did Google start sending this X-Frame-Options header? If it happens to be around the right time, we'll just change the test to do something more appropriate.

推荐答案

本文解释它是如何在2009年12月打破一些聊天软件的。所以至少已经有两年了。

This article explains how it broke some chat software in December 2009. So it's been at least two years.

这篇关于Google搜索何时开始发送X-Frame-Options：SAMEORIGIN？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！