RESOLVED FIXED 104285
[GTK] Add authentication support to DRT and fix exposed issues in the libsoup backend
https://bugs.webkit.org/show_bug.cgi?id=104285
Summary [GTK] Add authentication support to DRT and fix exposed issues in the libsoup...
Martin Robinson
Reported 2012-12-06 12:07:33 PST
This bug covers adding authentication support to DumpRenderTree and fixing any issues in ResourceHandleSoup that this exposes.
Attachments
Patch (26.21 KB, patch)
2012-12-08 11:22 PST, Martin Robinson
no flags
Properly handle authentication restarts in restartedCallback (30.01 KB, patch)
2012-12-08 16:42 PST, Martin Robinson
no flags
New patch with better comment explaining the null password issue (30.08 KB, patch)
2012-12-09 02:45 PST, Martin Robinson
gustavo: review+
Martin Robinson
Comment 1 2012-12-08 11:22:06 PST
Martin Robinson
Comment 2 2012-12-08 11:24:09 PST
This also requires a bump to the libsoup version in the jhbuild modules to fix a libsoup bug. I'll handle that in a separate patch.
Martin Robinson
Comment 3 2012-12-08 16:42:04 PST
Created attachment 178386 [details] Properly handle authentication restarts in restartedCallback
Dan Winship
Comment 4 2012-12-09 01:56:18 PST
Comment on attachment 178386 [details] Properly handle authentication restarts in restartedCallback View in context: https://bugs.webkit.org/attachment.cgi?id=178386&action=review > Source/WebCore/platform/network/soup/ResourceRequestSoup.cpp:146 > + // soup_uri_new will convert empty usernames and passwords into null. Some parts of > + // soup like the SoupAuthenticationManager will only be active when both the username > + // and password are non-null. When we have credentials, empty usernames and passwords > + // should be empty strings instead of null. This didn't sound right to me, so I added a test, and it does seem to work: http://git.gnome.org/browse/libsoup/commit/?id=66650e5 So, not sure what was failing for you. > Tools/DumpRenderTree/gtk/TestRunnerGtk.cpp:170 > + // soup_uri_to_string does not insert the password into the string, so we need to create the > + // URI string and then reinsert any credentials that were present in the SoupURI. All tests that > + // use URL-embedded credentials use HTTP, so it's safe here. you could add a soup_uri_to_string_with_password() (or something) if you want. Other people have wanted that before... > LayoutTests/platform/gtk/TestExpectations:-879 > -# No authentication challenge handling woooo > LayoutTests/platform/gtk/http/tests/misc/401-alternative-content-expected.txt:-1 > -PASS any reason we don't just print out the debug message to match the default expectation?
Dan Winship
Comment 5 2012-12-09 01:57:03 PST
(In reply to comment #4) > > LayoutTests/platform/gtk/http/tests/misc/401-alternative-content-expected.txt:-1 > > -PASS > > any reason we don't just print out the debug message to match the default expectation? oh, oops, that's a removal not an addition
Martin Robinson
Comment 6 2012-12-09 02:45:09 PST
Created attachment 178401 [details] New patch with better comment explaining the null password issue
Gustavo Noronha (kov)
Comment 7 2012-12-11 02:11:52 PST
Comment on attachment 178401 [details] New patch with better comment explaining the null password issue LGTM!
Martin Robinson
Comment 8 2012-12-12 11:21:11 PST
Note You need to log in before you can comment on or make changes to this bug.