From: Paul Orlyk <paul.orlyk@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: [FFmpeg-devel] [PATCH v2 1/2] avformat/rtsp: Support mode field of Transport header being sent in upper case Date: Mon, 15 Jan 2024 22:37:09 +0200 Message-ID: <775df95f-1e9a-431a-8dc9-33a1f4f651a5@gmail.com> (raw) In-Reply-To: <20240113182218.GE6420@pb2> Fixes server compatibility issues with rtspclientsink GStreamer plugin Signed-off-by: Paul Orlyk <paul.orlyk@gmail.com> --- libavformat/rtsp.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/libavformat/rtsp.c b/libavformat/rtsp.c index 583f5338e8..61e24a5c7a 100644 --- a/libavformat/rtsp.c +++ b/libavformat/rtsp.c @@ -1012,8 +1012,8 @@ static void rtsp_parse_transport(AVFormatContext *s, if (*p == '=') { p++; get_word_sep(buf, sizeof(buf), ";, ", &p); - if (!strcmp(buf, "record") || - !strcmp(buf, "receive")) + if (!av_strcasecmp(buf, "record") || + !av_strcasecmp(buf, "receive")) th->mode_record = 1; } } -- 2.43.0 _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2024-01-15 20:37 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-27 13:44 [FFmpeg-devel] [PATCH] avformat/rtsp: Fix server compatibility issues with rtspclientsink GStreamer plugin Paul Orlyk 2023-12-28 19:33 ` Michael Niedermayer 2024-01-03 12:51 ` Paul Orlyk 2024-01-10 17:57 ` Paul Orlyk 2024-01-12 19:07 ` Michael Niedermayer 2024-01-12 20:46 ` Paul Orlyk 2024-01-13 18:22 ` Michael Niedermayer 2024-01-15 20:37 ` Paul Orlyk [this message] 2024-01-16 0:05 ` [FFmpeg-devel] [PATCH v2 1/2] avformat/rtsp: Support mode field of Transport header being sent in upper case Michael Niedermayer 2024-01-15 20:37 ` [FFmpeg-devel] [PATCH v2 2/2] avformat/rtsp: Send mode=record instead of mode=receive in Transport header Paul Orlyk 2024-01-16 0:20 ` Michael Niedermayer
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=775df95f-1e9a-431a-8dc9-33a1f4f651a5@gmail.com \ --to=paul.orlyk@gmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git