resources/first-page.html - willSendRequest redirectResponse (null) go-back-cached-main-resource.html - didFinishLoading resources/first-page.html - didReceiveResponse resources/first-page.html - didFinishLoading resources/other-page.html - willSendRequest redirectResponse (null) resources/other-page.html - didReceiveResponse resources/other-page.html - didFinishLoading resources/first-page.html - willSendRequest redirectResponse (null) resources/first-page.html - didReceiveResponse resources/first-page.html - didFinishLoading resources/other-page.html - willSendRequest redirectResponse (null) resources/other-page.html - didReceiveResponse resources/other-page.html - didFinishLoading resources/first-page.html - willSendRequest redirectResponse (null) resources/first-page.html - didReceiveResponse resources/first-page.html - didFinishLoading This test check the following situation: First you navigate to a page (first-page.html). Then you go to another page (other-page.html). You repeat previous steps again (going to first-page.html and then to other-page.html). Finally you click back. The problem was that the resource load callbacks when going back to the cached main resource were not being called. See bug #112418.