mirror of https://github.com/FFmpeg/FFmpeg.git
If the string consists entirely of whitespace, this could in theory continue to write '\0' before the start of the memory allocation. In practice, it didn't really happen: the generic HTTP header parsing code already skips leading whitespaces, so the string is either empty, or consists a non-whitespace. (The generic code and the cookie code actually have different ideas about what bytes are whitespace: the former uses av_isspace(), the latter uses WHITESPACES. Fortunately, av_isspace() is a super set of the http.c specific WHITESPACES, so there's probably no case where the above assumption could have been broken.)pull/283/head
parent
c0687acbf6
commit
b7d842c554
1 changed files with 2 additions and 0 deletions
Loading…
Reference in new issue