Bug 125410

Summary: [Soup] Send original encoded data size to didReceiveBuffer
Product: WebKit Reporter: Martin Robinson <mrobinson>
Component: PlatformAssignee: Gustavo Noronha (kov) <gustavo>
Status: RESOLVED FIXED    
Severity: Normal CC: cdumez, commit-queue, danw, gustavo, rakuco
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch
none
Patch mrobinson: review+

Martin Robinson
Reported 2013-12-08 05:55:01 PST
didReceiveBuffer/didReceiveData accepts the original (encoded) data size, but the libsoup backend is always sending the decoded data size.
Attachments
Patch (5.18 KB, patch)
2013-12-08 07:07 PST, Gustavo Noronha (kov)
no flags
Patch (5.85 KB, patch)
2013-12-09 11:01 PST, Gustavo Noronha (kov)
mrobinson: review+
Gustavo Noronha (kov)
Comment 1 2013-12-08 07:07:11 PST
Dan Winship
Comment 2 2013-12-08 23:53:36 PST
Comment on attachment 218687 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=218687&action=review > Source/WebCore/platform/network/soup/ResourceHandleSoup.cpp:607 > + while (!G_IS_SEEKABLE(baseStream)) > + baseStream = g_filter_input_stream_get_base_stream(G_FILTER_INPUT_STREAM(baseStream)); This assumes you will always eventually find a seekable stream... does this code get used for non-http requests as well? (eg, data: URIs) Also, be sure to test that it works right with resources returned from cache
Gustavo Noronha (kov)
Comment 3 2013-12-09 05:51:30 PST
I'm going to run the tests in debug mode and test that it's working with cached resources (though I think the inspector treats those specially). I'm pretty sure the data: URIs use that code indeed, good catch!
Gustavo Noronha (kov)
Comment 4 2013-12-09 11:01:59 PST
Martin Robinson
Comment 5 2013-12-09 11:26:49 PST
Comment on attachment 218778 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=218778&action=review > Source/WebCore/platform/network/soup/ResourceHandleSoup.cpp:739 > + d->m_previousPosition = handle->currentStreamPosition(); > + Maybe try removing this...
Gustavo Noronha (kov)
Comment 6 2013-12-10 02:04:40 PST
Note You need to log in before you can comment on or make changes to this bug.