The following layout test is failing on GTK http/tests/loading/authentication-after-redirect-stores-wrong-credentials/authentication-after-redirect-stores-wrong-credentials.html After r153852 <http://trac.webkit.org/changeset/153852>, URLs displayed as <unknown> started being shown properly. In the GTK port, r154098 <http://trac.webkit.org/changeset/154098> provided that implementation, and after that, it seems that a different, hidden issue, was shown: --- /home/slave/webkitgtk/gtk-linux-64-release/build/layout-test-results/http/tests/loading/authentication-after-redirect-stores-wrong-credentials/authentication-after-redirect-stores-wrong-credentials-expected.txt +++ /home/slave/webkitgtk/gtk-linux-64-release/build/layout-test-results/http/tests/loading/authentication-after-redirect-stores-wrong-credentials/authentication-after-redirect-stores-wrong-credentials-actual.txt @@ -3,7 +3,7 @@ frame "<!--framePath //<!--frame0-->-->" - didStartProvisionalLoadForFrame main frame - didFinishDocumentLoadForFrame frame "<!--framePath //<!--frame0-->-->" - didReceiveServerRedirectForProvisionalLoadForFrame -http://localhost:8000/loading/authentication-after-redirect-stores-wrong-credentials/resources/wrong-credential-1-redirect-to-auth.php - didReceiveAuthenticationChallenge - Responding with httpUsername:httpPassword +http://127.0.0.1:8000/loading/authentication-after-redirect-stores-wrong-credentials/resources/wrong-credential-2-auth-then-redirect-to-finish.php - didReceiveAuthenticationChallenge - Responding with httpUsername:httpPassword frame "<!--framePath //<!--frame0-->-->" - didCommitLoadForFrame frame "<!--framePath //<!--frame0-->-->" - didFinishDocumentLoadForFrame frame "<!--framePath //<!--frame0-->-->" - didHandleOnloadEventsForFrame So there seems to be a problem with the redirection.
This test is passing now in the bot and locally. Test expectation will be updated accordingly. Simon, please confirm and close.
(In reply to comment #1) > This test is passing now in the bot and locally. Test expectation will be updated accordingly. > > Simon, please confirm and close. Checking. I'll let you know in a moment.
Yes: this bug is no longer failing.