If you encounter a specific operation that you wish to do, but are prevented from because of the maxiumum content length, I recommend creating an issue and providing in it an example of that operation. That way the best way of resolving your problem, whether just changing the content length maximum, or possibly even making other changes in the api to avoid the limit -- can be accomplished.
On Thu, Mar 5, 2015 at 8:09 AM, Claudiu Olteanu <olteanu.claudiu@xxxxxxxxx> wrote:
Thanks for your response.>> 1. Was this the desired design? If this is the case I believe that it>> would be better to write this limitation on the ARIdocumentation.
>
> It was intentional, but can be revisited.
What procedure should I follow for the revision of this problem? Should I open a new issue/bug? Will you transmit the problem further?All the best,Claudiu
_______________________________________________
asterisk-app-dev mailing list
asterisk-app-dev@xxxxxxxxxxxxxxxx
http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev
Scott Griepentrog
Digium, Inc · Software Developer
445 Jan Davis Drive NW · Huntsville, AL 35806 · US
direct/fax: +1 256 428 6239 · mobile: +1 256 580 6090
Check us out at: http://digium.com · http://asterisk.org
Digium, Inc · Software Developer
445 Jan Davis Drive NW · Huntsville, AL 35806 · US
direct/fax: +1 256 428 6239 · mobile: +1 256 580 6090
Check us out at: http://digium.com · http://asterisk.org
_______________________________________________ asterisk-app-dev mailing list asterisk-app-dev@xxxxxxxxxxxxxxxx http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev
