You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shindig.apache.org by "Ryan Baxter (JIRA)" <ji...@apache.org> on 2012/05/30 14:46:31 UTC

[jira] [Updated] (SHINDIG-1752) When the property gadgets.jsonProxyUrl.maxPostSize is missing from the container.js the default post size ends up being 0 instead of using the default value

     [ https://issues.apache.org/jira/browse/SHINDIG-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ryan Baxter updated SHINDIG-1752:
---------------------------------

    Fix Version/s:     (was: 2.5.0)
                   2.5.0-beta2
    
> When the property gadgets.jsonProxyUrl.maxPostSize is missing from the container.js the default post size ends up being 0 instead of using the default value
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SHINDIG-1752
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-1752
>             Project: Shindig
>          Issue Type: Bug
>    Affects Versions: 2.5.0
>            Reporter: Ryan Baxter
>            Assignee: Ryan Baxter
>             Fix For: 2.5.0-beta2
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> If a container.js is missing gadgets.jsonProxyUrl.maxPostSize the default post size will be 0 instead of the actual default size because ContainerConfig.getInt returns 0 when the property is missing not null.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira