[
https://issues.apache.org/jira/browse/AMBARI-13338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947040#comment-14947040
]
Hudson commented on AMBARI-13338:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #3607 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3607/])
AMBARI-13338 Ambari Web should surface HTTP 413 error. (atkach) (atkach:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=15ac283641e22a5c1ce25a24020480ade79ffd0e])
* ambari-web/app/utils/ajax/ajax.js
> Ambari Web should surface HTTP 413 error
> ----------------------------------------
>
> Key: AMBARI-13338
> URL: https://issues.apache.org/jira/browse/AMBARI-13338
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.1.1
> Reporter: Andrii Tkach
> Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13338.patch
>
>
> {quote}
> It looked to me like application was silently failing with 1 API call failing
> due to HTTP 413 error on the bad firefox. This was an environment issue but
> ambari-web should have surfaced the issue on UI showing API call failure.
> {quote}
> The 413 was because of "Request entity too large"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
