After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 709371 - souphttpsrc: Need to issue HEAD while in READY state
souphttpsrc: Need to issue HEAD while in READY state
Status: RESOLVED INVALID
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
1.x
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-10-03 14:31 UTC by Lori Anderson
Modified: 2013-10-03 15:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Lori Anderson 2013-10-03 14:31:59 UTC 
In gst_soup_http_src_check_seekable(), the current state check requires "paused" or greater.  It should also allow for gathering the information about the content when in the "ready" state. 

This line:

  if (!src->got_headers && GST_STATE (src) >= GST_STATE_PAUSED) {

Should be changed to:

  if (!src->got_headers && GST_STATE (src) >= GST_STATE_READY) {


Version Info:
Plugin Details:
  Name                     soup
  Description              libsoup HTTP client src/sink
  Filename                 /home/landerson/gst/git/gst-plugins-good/ext/soup/.libs/libgstsouphttpsrc.so
  Version                  1.3.0.1
  License                  LGPL
  Source module            gst-plugins-good
  Source release date      2013-10-03 01:44 (UTC)
  Binary package           GStreamer Good Plug-ins git
  Origin URL               Unknown package origin
Comment 1 Tim-Philipp Müller 2013-10-03 14:38:04 UTC 
Please could you describe your specific use case in more detail.

See bug #705371 for why the code is not as requested.
Comment 2 Lori Anderson 2013-10-03 15:09:35 UTC 
Thanks for the reference to Bug #705371.  This also impacts changes to Bug #309371.  I will investigate how to delay the HEAD request until pipeline is in the "PAUSED" state.  This bug can be closed :).