RESOLVED FIXED 142164
[SOUP] Use SoupMessage::starting instead of SoupSession::request-started
https://bugs.webkit.org/show_bug.cgi?id=142164
Summary [SOUP] Use SoupMessage::starting instead of SoupSession::request-started
Carlos Garcia Campos
Reported 2015-03-02 05:52:17 PST
SoupSession::request-started is deprecated in libsoup 2.50. Both signals are equivalent, but SoupMessage::starting is also emitted for resources loaded from the disk cache. This fixes web timing calculations for cached resources, since we were not initializing m_requestStart.
Attachments
Patch (3.81 KB, patch)
2015-03-02 05:54 PST, Carlos Garcia Campos
svillar: review+
Carlos Garcia Campos
Comment 1 2015-03-02 05:54:12 PST
Sergio Villar Senin
Comment 2 2015-03-02 06:15:07 PST
Comment on attachment 247662 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=247662&action=review Makes sense. Any test that could start have started to pass due to this change? > Source/WebCore/platform/network/soup/SoupNetworkSession.cpp:119 > #endif Pretty unfortunate to have the WebTiming stuff here. Hopefully we could remove it with the starting signal at some point.
Carlos Garcia Campos
Comment 3 2015-03-02 06:19:48 PST
(In reply to comment #2) > Comment on attachment 247662 [details] > Patch Thanks! > View in context: > https://bugs.webkit.org/attachment.cgi?id=247662&action=review > > Makes sense. Any test that could start have started to pass due to this > change? I've tried all webtiming tests in TestExpectations before the patch and all of them passed, so . . . Anyway, this only affects disk cached resources, so I guess that's not the case of any test. > > Source/WebCore/platform/network/soup/SoupNetworkSession.cpp:119 > > #endif > > Pretty unfortunate to have the WebTiming stuff here. Hopefully we could > remove it with the starting signal at some point. Yes, indeed.
Carlos Garcia Campos
Comment 4 2015-03-03 02:25:17 PST
Note You need to log in before you can comment on or make changes to this bug.