view src/os/win32/nginx_icon16.xpm @ 9049:a10210a45c8b

Core: stricter UTF-8 handling in ngx_utf8_decode(). An UTF-8 octet sequence cannot start with a 11111xxx byte (above 0xf8), see https://datatracker.ietf.org/doc/html/rfc3629#section-3. Previously, such bytes were accepted by ngx_utf8_decode() and misinterpreted as 11110xxx bytes (as in a 4-byte sequence). While unlikely, this can potentially cause issues. Fix is to explicitly reject such bytes in ngx_utf8_decode().
author Yugo Horie <u5.horie@gmail.com>
date Thu, 23 Feb 2023 08:09:50 +0900
parents 4ac89c5aa10d
children
line wrap: on
line source

/* XPM */
static char * nginx_xpm[] = {
"16 16 2 2",
/* colors */
"   c none",
"GG c #009900",
/* pixels */
"                                ",
"        GGGGGGGGGGGGGGGG        ",
"        GGGGGGGGGGGGGGGG        ",
"      GGGGGGGGGGGGGGGGGGGG      ",
"      GGGGGG        GGGGGG      ",
"    GGGGGG            GGGGGG    ",
"    GGGGGG                      ",
"  GGGGGG      GGGGGGGGGGGGGGGG  ",
"  GGGGGG    GGGGGGGGGGGGGGGGGG  ",
"    GGGGGG    GGGGGGGGGGGGGG    ",
"    GGGGGG            GGGGGG    ",
"      GGGGGG        GGGGGG      ",
"      GGGGGGGGGGGGGGGGGGGG      ",
"        GGGGGGGGGGGGGGGG        ",
"        GGGGGGGGGGGGGGGG        ",
"                                "
};