Souphttpsrc 'error: Server does not support seeking'

[Hans Maree]

After some further investigation using tcpdump and wireshark I tracked down
the
source of the errors. It seems that the connection is interrupted (It is a
wireless connection so this happens from time to time) just before the
errors
occur.

The souphttpsrc element then sends a new request to the ip-camera as
expected,
however it adds a Range HTTP header field to the request. The ip-camera
ignores
the Range header field since it serves a live stream. The souphttpsrc then
sends the warnings I mentioned in my previous post and closes the
connection.

So this seems to be a bug in souphttpsrc, since I have indicated that the
source is a live source by specifying 'is_live=true', so to my understanding
it
should not try to seek at all, or at least not break when the server ignores
the Range header field.

Before I file a bug report I would like to be sure it is indeed a bug, so
please give some feedback on that matter.  Also does anyone know a
workaround
to this problem? I am using the ip-camera as security camera so I would like
to
make it reliable as soon as possible.

By the way I am using the following versions of gstreamer and plugins:
gstreamer0.10 0.10.35.2 (pre release) 
gstreamer0.10-base 0.10.35.2 (pre release)
gstreamer0.10-base-plugins 0.10.35.2 (pre release)
gstreamer0.10-good 0.10.30.2 (pre release)

--
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/Souphttpsrc-error-Server-does-not-support-seeking-tp4239793p4254350.html
Sent from the GStreamer-devel mailing list archive at Nabble.com.