From: Marton Balint <cus@passwd.hu>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] libavformat/http.c: cookie path attribute should be optional not compulsory
Date: Wed, 8 Mar 2023 23:45:30 +0100 (CET)
Message-ID: <523026bf-4fea-b41b-1f22-9b941994cd7@passwd.hu> (raw)
In-Reply-To: <9F880AE4-B819-4FBB-B086-54DD9984D80D@gmail.com>
On Fri, 3 Mar 2023, Michael J. Walsh wrote:
> The path attribute in the Set-Cookie header is optional but treated by ffmpeg as being compulsory.
>
> Signed-off-by: Michael J. Walsh <mjfwalsh@gmail.com>
> —--
> libavformat/http.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Thanks, will apply.
Regards,
Marton
>
> diff --git a/libavformat/http.c b/libavformat/http.c
> index 7bce821535..dde22a7e09 100644
> --- a/libavformat/http.c
> +++ b/libavformat/http.c
> @@ -1293,9 +1293,9 @@ static int get_cookies(HTTPContext *s, char **cookies, const char *path,
> goto skip_cookie;
> }
>
> - // ensure this cookie matches the path
> + // if a cookie path is provided, ensure the request path is within that path
> e = av_dict_get(cookie_params, "path", NULL, 0);
> - if (!e || av_strncasecmp(path, e->value, strlen(e->value)))
> + if (e && av_strncasecmp(path, e->value, strlen(e->value)))
> goto skip_cookie;
>
> // cookie parameters match, so copy the value
> --
> 2.30.2
>
>
> _______________________________________________
> 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".
_______________________________________________
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".
prev parent reply other threads:[~2023-03-08 22:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 16:24 Michael J. Walsh
2023-03-08 22:45 ` Marton Balint [this message]
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=523026bf-4fea-b41b-1f22-9b941994cd7@passwd.hu \
--to=cus@passwd.hu \
--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