Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot upload annotation files larger than 1 MB (413 Request Entity Too Large) #4679

Closed
ninafiona opened this issue Jun 8, 2022 · 2 comments

Comments

@ninafiona
Copy link

I sucessfully created a task with 750 images and now want to upload an annotation file (COCO) that is of file size 1.2MB. I get the following error:

Failed to load resource: the server responded with a status of 413 ()
cvat-app.tsx:262 Error: Request failed with status code 413. "<html>\r\n<head><title>413 Request Entity Too Large</title></head>\r\n<body>\r\n<center><h1>413 Request Entity Too Large</h1></center>\r\n<hr><center>nginx/1.21.6</center>\r\n</body>\r\n</html>\r\n<!-- a padding to disable MSIE and Chrome friendly error page -->\r\n<!-- a padding to disable MSIE and Chrome friendly error page -->\r\n<!-- a padding to disable MSIE and Chrome friendly error page -->\r\n<!-- a padding to disable MSIE and Chrome friendly error page -->\r\n<!-- a padding to disable MSIE and Chrome friendly error page -->\r\n<!-- a padding to disable MSIE and Chrome friendly error page -->\r\n".

I tried removing some annotations which shrunk the file size to 800kB and then the upload succeeded. How can I upload larger files?

@ninafiona ninafiona changed the title Cannot upload annotation file larger than 1 MB (413 Request Entity Too Large) Cannot upload annotation files larger than 1 MB (413 Request Entity Too Large) Jun 8, 2022
@Marishka17
Copy link
Contributor

I'll close this issue because It should be fixed in PR. Please try the latest CVAT version and don't hesitate to reopen the issue if it is still relevant.

@stevezkw1998
Copy link

@Marishka17 The fix for this issue was on Mar 11, 2022
However this issue also happened in 2.7.2 which was released on Sep 26

It doesn't make sense why later version still has this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants