[Bug 795176] souphttpsrc: Reading in too big blocksizes can cause the connection to time out

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=795176

Sebastian Dröge (slomo) <slomo at coaxion.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|HTTP Transport              |gst-plugins-good
            Version|2.62.x                      |git master
           Assignee|libsoup-maint at gnome.bugs    |gstreamer-bugs at lists.freede
                   |                            |sktop.org
            Product|libsoup                     |GStreamer
   Target Milestone|---                         |git master
            Summary|g_input_stream_read()       |souphttpsrc: Reading in too
                   |returns 0 bytes before the  |big blocksizes can cause
                   |end of the stream           |the connection to time out
         QA Contact|libsoup-maint at gnome.bugs    |gstreamer-bugs at lists.freede
                   |                            |sktop.org

--- Comment #11 from Sebastian Dröge (slomo) <slomo at coaxion.net> ---
Ah nevermind, missed the last comment. Yeah so on the GStreamer side it should
not just read 0 but also get an GError that the connection was closed, or not?

For the solution, I don't really know. Limiting the block-size is an option of
course, but there's always a trade-off here. Lower block-sizes have lower
latency and higher overhead, and the opposite for bigger block-sizes.

A property could make sense, but ideally we could solve this without requiring
any settings.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.