diff options
| author | Alexander Strasser <eclipse7@gmx.net> | 2017-03-11 15:43:39 +0100 |
|---|---|---|
| committer | Alexander Strasser <eclipse7@gmx.net> | 2017-03-14 22:58:53 +0100 |
| commit | a70d5e25936424112ecbeb1c304100e68bce0faa (patch) | |
| tree | 81ce2b56f70ffe391d071e74d771f5098b10f4a3 /libavformat/avio.c | |
| parent | 6693d57e99d9bde450b145024f025e5c5349c3a0 (diff) | |
| download | ffmpeg-a70d5e25936424112ecbeb1c304100e68bce0faa.tar.gz | |
lavf/avio: Be more explicit in logging white/black list matches
The current form of the messages indicating matches in the white
or black lists seems to be a bit too much relying on context.
Make the messages more explicit.
Signed-off-by: Alexander Strasser <eclipse7@gmx.net>
Diffstat (limited to 'libavformat/avio.c')
| -rw-r--r-- | libavformat/avio.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/libavformat/avio.c b/libavformat/avio.c index 9020aa91e4..1e79c9dd5c 100644 --- a/libavformat/avio.c +++ b/libavformat/avio.c @@ -179,12 +179,12 @@ int ffurl_connect(URLContext *uc, AVDictionary **options) (uc->protocol_blacklist && !strcmp(uc->protocol_blacklist, e->value))); if (uc->protocol_whitelist && av_match_list(uc->prot->name, uc->protocol_whitelist, ',') <= 0) { - av_log(uc, AV_LOG_ERROR, "Protocol not on whitelist '%s'!\n", uc->protocol_whitelist); + av_log(uc, AV_LOG_ERROR, "Protocol '%s' not on whitelist '%s'!\n", uc->prot->name, uc->protocol_whitelist); return AVERROR(EINVAL); } if (uc->protocol_blacklist && av_match_list(uc->prot->name, uc->protocol_blacklist, ',') > 0) { - av_log(uc, AV_LOG_ERROR, "Protocol blacklisted '%s'!\n", uc->protocol_blacklist); + av_log(uc, AV_LOG_ERROR, "Protocol '%s' on blacklist '%s'!\n", uc->prot->name, uc->protocol_blacklist); return AVERROR(EINVAL); } |