GNOME Bugzilla – Bug 552506
[neonhttpsrc] doesn't handle/throw errors correctly
Last modified: 2008-09-17 14:24:47 UTC
Please describe the problem: All the errors it throws are in the LIBRARY INIT category, this is completely wrong. For example, accessing a URL that requires authorization and giving a 401 gives: ERROR: Pipeline doesn't want to pause. ERROR: from element /pipeline0/neonhttpsrc0: Could not initialize supporting library. Additional debug info: gstneonhttpsrc.c(600): gst_neonhttp_src_start (): /pipeline0/neonhttpsrc0: Could not begin request (0) I see a bunch of other errors that get thrown in LIBRARY INIT, which is *purely* for problems with initializing the library, and *not at all* specific to the resource being opened. Steps to reproduce: 1. 2. 3. Actual results: Expected results: Does this happen every time? Other information:
Shocking! Fixed (patch would've been nice...): 2008-09-17 Tim-Philipp Müller <tim.muller at collabora co uk> * ext/neon/gstneonhttpsrc.c: (gst_neonhttp_src_start): Don't post LIBRARY_INIT errors where we should be posting RESOURCE OPEN_READ errors. Fixes #552506.