Google 搜索何时开始发送 X-Frame-Options: SAMEORIGIN？
我对我们的应用程序进行了自动化测试，其中包括在 IFrame 中显示 Google 搜索框。该测试最近开始失败，一名开发人员签入的更改破坏了其他几个测试。我开始怀疑这个改变是否破坏了这个测试，但我很想知道。截至目前，我可以看到 Google 搜索（ie、http: //www.google.com/search?q=whatever) 返回带有 SAMEORIGIN 的 X-Frame-Options 标头，告诉浏览器不要显示我们的 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.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
本文 解释了它如何在 2009 年 12 月破坏了一些聊天软件。所以至少已经过去两年了。
This article explains how it broke some chat software in December 2009. So it's been at least two years.