Bug 1172393 - File cannot be pushed to zanata, error status 413
Summary: File cannot be pushed to zanata, error status 413
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Zanata
Classification: Retired
Component: Component-UI
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Damian Jansen
QA Contact: Zanata-QA Mailling List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-10 01:13 UTC by Terry CHUANG
Modified: 2015-06-15 13:10 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-12-14 23:21:04 UTC
Embargoed:


Attachments (Terms of Use)
The file that was causing Error status 413 while pushing to zanata (1.06 MB, application/x-xliff)
2014-12-10 01:13 UTC, Terry CHUANG
no flags Details

Description Terry CHUANG 2014-12-10 01:13:09 UTC
Created attachment 966567 [details]
The file that was causing Error status 413 while pushing to zanata

Description of problem:
File cannot be pushed to zanata, possible cause might be the size of the file.

Actual results:
Returned Error status "413 Request Entity Too Large".

The project to push this file to is located at: https://translate.engineering.redhat.com/iteration/view/rhn-satellite-ui/5.7

I have attached the problematic .xml file to this bug.

Thank you for your help.

Regards,
Terry

Comment 1 Ding-Yi Chen 2014-12-10 01:53:31 UTC
Last time I check the project type is "Unspecified". You won't be able to push for an "unspecified" push type.

Comment 2 David Mason 2014-12-11 05:33:40 UTC
The problem was caused by nginx congfiguration of the server, and should now be fixed.

Please note that the attached file contains 2 empty trans units, which are invalid. After deleting both the elements starting with <trans-unit id=""> I was able to push the file to the staging server with the nginx fix applied.

I am not able to attempt upload to the production server because I do not have the proper path for the attached file, so I will await confirmation that the push was successful. Please let me know whether push is successful and I will mark the resolution for this bug. I will make sure I am on #zanata on Freenode this evening to provide further assistance if it is needed.

Comment 3 David Mason 2014-12-14 23:21:04 UTC
The file was able to be pushed to Zanata once the nginx configuration was updated. Specifically by adding `client_max_body_size 10m;` in /etc/nginx/conf.d/jboss-proxy.conf

Comment 4 Terry CHUANG 2015-06-15 13:10:18 UTC
The bug has been resolved.


Note You need to log in before you can comment on or make changes to this bug.