[Webkit-unassigned] [Bug 126242] [SOUP] Response body are always NULL.

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=126242





--- Comment #2 from Aleksandr <aleks.a.kozlov at gmail.com>  2013-12-26 05:27:28 PST ---
(In reply to comment #1)
> (In reply to comment #0)
> > I get current WebKit's SoupSession and SoupMesssage in Injectedbundle using "request-queued" signal throw g_signal_add_emission_hook. But the response_body of SoupMessageBody are always NULL.
> 
> request-queued means that the request was added to the SoupSession queue and is ready to be processed. The request was not even sent to the server at that moment. Check libsoup's documentation for more information about the signals, like for example here:
> 
> https://developer.gnome.org/libsoup/stable/SoupSession.html#SoupSession-request-queued

Thanks for the answer. Yes, you are rigth about "request-queued" signal.
But in "request-queued" signal I get the SoupSession and assign SoupMessage callbacks ("wrote-body", "got-body", "wrote-chunk" etc).
I trying to get responce SoupMessageBody in "got-body" SoupMessage signal.
Note that "got-chunk" signal doesn't emit, I think because the response body are empty.
In libsoup's documentation says: If you are using SoupRequest (as I know WebKit uses SoupRequest), then the message body is not accumulated by default, so response_body's data will always be NULL.

https://developer.gnome.org/libsoup/stable/SoupMessage.html#SoupMessage-struct

Thanks.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.