[asterisk-bugs] [JIRA] (ASTERISK-23503) Using AMI via HTTP adds extra characters (: and space) to some request headers.

[Rusty Newton (JIRA)]

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

Rusty Newton commented on ASTERISK-23503:
-----------------------------------------

Talked with Matt Jordan that confirmed this is undefined behavior. If you form the URL correctly it works.

Of course, patches are always welcome if someone wants to work on making the parsing more robust. Closing this out until there is a patch.

Thanks for the report. I'll make sure the proper URL syntax is documented on the wiki pages for AJAM/AMI over HTTP.

> Using AMI via HTTP adds extra characters (: and space) to some request headers.
> -------------------------------------------------------------------------------
>
>                 Key: ASTERISK-23503
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23503
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/HTTP
>    Affects Versions: 11.8.1
>         Environment: CentOS
>            Reporter: André Maricato
>
> Hy.
> So, I searched the issue tracker for this problem but didn't find anything like it so I'm submitting this as a new issue. Hope I'm not doing anything wrong...
> So, what I found is that, when making an AMI request via HTTP with the Request URL like:
> /asterisk/manager?action=Originate&Channel:<channel>&Application:<application>
> I get on asterisk debug an extension not found in context error because the channel, context and application (in this particular request) get extra ":" and "space" characters at the end of the string. If I add those two characters to the end of the used context names in the request, everything works.
> I hope I was explicit enough.
> Best regards,
> André.



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