[
https://issues.apache.org/jira/browse/AIRAVATA-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830492#comment-15830492
]
ASF subversion and git services commented on AIRAVATA-1397:
-----------------------------------------------------------
Commit 71f32f4ee5c3eb200750f22aaf45692f3d45c308 in airavata-php-gateway's
branch refs/heads/develop from [~marcuschristie]
[ https://git-wip-us.apache.org/repos/asf?p=airavata-php-gateway.git;h=71f32f4 ]
AIRAVATA-1397 Set upload_max_filesize to 64M in .htaccess
These settings in .htaccess override whatever is in /etc/php.ini. This
provides a better out of the box default max upload size.
> PGA gateway needs to gracefully handle attempts to upload files that are too
> large.
> -----------------------------------------------------------------------------------
>
> Key: AIRAVATA-1397
> URL: https://issues.apache.org/jira/browse/AIRAVATA-1397
> Project: Airavata
> Issue Type: Improvement
> Reporter: Marlon Pierce
> Assignee: Marcus Christie
> Fix For: 0.17
>
>
> This is mostly a PHP problem. File upload limits are specified in the
> php.ini file (typically, /etc/php.ini). The parameters upload_max_filesize
> and post_max_size need to be modified to increase the size.
> If post_max_size is exceeded, the operation will fail silently: PHP doesn't
> complain, and PGA will not call the airavata clients. If upload_max_filesize
> is exceeded but not the post size limit, you will get errors. It is
> advisable to change both (as documented in the PGA's README.md file) and to
> keep both the same value.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
