[gstreamer-bugs] [Bug 588777] New: [souphttpsrc] don't try to authenticate if no username/password is set

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=588777

  GStreamer | gst-plugins-good | Ver: git
           Summary: [souphttpsrc] don't try to authenticate if no
                    username/password is set
           Product: GStreamer
           Version: git
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-good
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: arnout at mind.be
         QAContact: gstreamer-bugs at lists.sourceforge.net
                CC: arnout at mind.be
     GNOME version: Unspecified
   GNOME milestone: Unspecified


When souphttpsrc receives the "authenticate" signal from soup, it tries to
authenticate the connection with the username and password that are set as
properties on the element.  However, if username or password are NULL, this
triggers a 

libsoup-CRITICAL **: soup_auth_authenticate: assertion `username != NULL'
failed

The attached patch doesn't try to authenticate if username or password is NULL.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=588777.