[asterisk-bugs] [JIRA] (ASTERISK-27072) AMI response contains order-important headers, violating AMI v2 spec

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-27072:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

> AMI response contains order-important headers, violating AMI v2 spec
> --------------------------------------------------------------------
>
>                 Key: ASTERISK-27072
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27072
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_queue, Core/ManagerInterface
>    Affects Versions: 14.5.0, GIT
>            Reporter: Brian
>
> Some AMI actions result in responses that contain ordered headers, but the AMI v2 protocol specification says that header order does not matter.
> One example of an AMI action that violates the unordered behavior is QueueRule/manager_queue_rule_show(), which [outputs RuleList and Rule header pairs where each Rule header is associated with the RuleList header that precedes it|https://github.com/asterisk/asterisk/blob/2e7866ebb7773fdd4f67e80f3747e41d84bcb93b/apps/app_queue.c#L9759-L9762].



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