[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=216857#comment-216857 ] 

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

Well, you should be calling the URL with equals signs in place of your colons. As follows:

{{asterisk/manager?action=Originate&Channel=<channel>&Application=<application>}}

That works fine in my testing.

That being said, using commas does result in the behavior you describe. That may be undefined behavior and maybe a bug or oversight. I'll see if a developer can confirm.

> 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)