[asterisk-bugs] [JIRA] (ASTERISK-24883) HTTP max content length - repercussions on ARI service

[Claudiu Olteanu (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-24883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claudiu Olteanu updated ASTERISK-24883:
---------------------------------------

    Description: 
This issue is related to the maximum content length for the body of an application/JSON.

I understand that it was done to provide a sane maximum to prevent an excessively large amount.

This limitation occurs when you want to raise an event to a user or to send a message to an endpoint (using the ARI service) and to attach some information to the body content using the variables parameter. 
If the body content length is greater than 4096, then the request will fail because it tries to get the body of the HTTP request using the ast_http_get_contents method which has this restriction. This limitation doesn't happen when you want to retrieve the information about all the endpoints from the system using a GET HTTP request to /endpointsURI, even if the content length of the response is greater than 4096.

In my scenario I use the ARI service to create a subscription service which holds some specific information about the endpoints (information related to the role of the subscriber). When then number of the endpoints is big (~100), then the subscription service fails to send its information to the users because it reaches the restriction of 4K. This is not the only application which uses the ARI application and reaches that limitation.

Therefore I was wondering if you can remove this limitation or make it configurable.

Best wishes,
Claudiu

  was:
This issue is related to the maximum content length for the body of an application/JSON.
I understand that it was done to provide a sane maximum to prevent an excessively large amount.

This limitation occurs when you want to raise an event to a user or to send a message to an endpoint (using the ARI service) and to attach some information to the body content using the variables parameter. 
If the body content length is greater than 4096, then the request will fail because it tries to get the body of the HTTP request using the ast_http_get_contents method which has this restriction. This limitation doesn't happen when you want to retrieve the information about all the endpoints from the system using a GET HTTP request to /endpointsURI, even if the content length of the response is greater than 4096.

In my scenario I use the ARI service to create a subscription service which holds some specific information about the endpoints (information related to the role of the subscriber). When then number of the endpoints is big (~100), then the subscription service fails to send its information to the users because it reaches the restriction of 4K. This is not the only application which uses the ARI application and reaches that limitation.

Therefore I was wondering if you can remove this limitation or make it configurable.

Best wishes,
Claudiu


> HTTP max content length - repercussions on ARI service
> ------------------------------------------------------
>
>                 Key: ASTERISK-24883
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24883
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Core/HTTP
>    Affects Versions: 13.0.0-beta1, 13.0.0-beta2, 13.0.0-beta3, 13.0.0, 13.0.1, 13.0.2, 13.1.0, 13.1.1, 13.2.0
>         Environment: Centos 6.5 - x86_64
>            Reporter: Claudiu Olteanu
>              Labels: ARI, Stasis, http
>
> This issue is related to the maximum content length for the body of an application/JSON.
> I understand that it was done to provide a sane maximum to prevent an excessively large amount.
> This limitation occurs when you want to raise an event to a user or to send a message to an endpoint (using the ARI service) and to attach some information to the body content using the variables parameter. 
> If the body content length is greater than 4096, then the request will fail because it tries to get the body of the HTTP request using the ast_http_get_contents method which has this restriction. This limitation doesn't happen when you want to retrieve the information about all the endpoints from the system using a GET HTTP request to /endpointsURI, even if the content length of the response is greater than 4096.
> In my scenario I use the ARI service to create a subscription service which holds some specific information about the endpoints (information related to the role of the subscriber). When then number of the endpoints is big (~100), then the subscription service fails to send its information to the users because it reaches the restriction of 4K. This is not the only application which uses the ARI application and reaches that limitation.
> Therefore I was wondering if you can remove this limitation or make it configurable.
> Best wishes,
> Claudiu



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