问题
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.
回答1:
This article explains how it broke some chat software in December 2009. So it's been at least two years.
来源：https://stackoverflow.com/questions/7905169/when-did-google-search-start-sending-x-frame-options-sameorigin