rtspsrc: Don't replace 404 errors with "no auth protocol found"
authorJan Alexander Steffens (heftig) <jan.steffens@ltnglobal.com>
Tue, 15 Nov 2022 10:56:35 +0000 (11:56 +0100)
committerGStreamer Marge Bot <gitlab-merge-bot@gstreamer-foundation.org>
Tue, 22 Nov 2022 13:07:17 +0000 (13:07 +0000)
commit1d7c936db073151a552f0e6759f31caf867998dc
treec46fca8dba95c3b1903c7be49cd83b9f804741ff
parent261290d1e675796df283a82ea1c345ac98b3097f
rtspsrc: Don't replace 404 errors with "no auth protocol found"

When getting a "404 Not Found" response from the DESCRIBE request, the
source produced a "No supported authentication protocol was found" error
instead of passing on the 404, which was confusing.

Only produce this error message when we're handling a response of "401
Unauthorized" without a compatible WWW-Authenticate header.

Part-of: <https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/3414>
subprojects/gst-plugins-good/gst/rtsp/gstrtspsrc.c