[asterisk-bugs] [JIRA] (ASTERISK-28667) Asterisk ignores parsing of config files if a Byte order mark is present

[Kevin Harwell (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-28667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249124#comment-249124 ] 

Kevin Harwell commented on ASTERISK-28667:
------------------------------------------

[~seanbright] Any thoughts on this, or do you still have the patch around to attach here or push up to gerrit - if so inclined of course :-)

> Asterisk ignores parsing of config files if a Byte order mark is present
> ------------------------------------------------------------------------
>
>                 Key: ASTERISK-28667
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28667
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Configs/Basic-PBX
>    Affects Versions: 16.5.1
>         Environment: CentOS 7
>            Reporter: Robin Leffmann
>
> If a Byte order mark ("BOM") is present in a .conf file, Asterisk will incorrectly state in the log that it has parsed the file but will in effect actually skip the file entirely, without throwing a warning or error.
> The BOM is a series of three bytes, 0xEF 0xBB 0xBF, represented by Unicode code point U+FEFF, and is typically located at the very start of a text file, and sometimes at the start of one or more lines in a text file.
> A test patch prodced and offered by [~seanbright] on IRC proved to solve the problem.



--
This message was sent by Atlassian JIRA
(v6.2#6252)