Artifactory "413 Request Entity Too Large" upload in CI

The upload was rejected with HTTP 413 because the artifact exceeds a size limit, usually a reverse proxy body-size cap in front of Artifactory rather than Artifactory itself.

What this error means

A jf rt upload or docker push of a large artifact fails with "413 Request Entity Too Large", often returning an nginx error page.

[Error] server response: 413 Request Entity Too Large
<html><head><title>413 Request Entity Too Large</title></head>
<body><center><h1>413 Request Entity Too Large</h1></center></body></html>

Common causes

A reverse proxy body-size limit

An nginx or load balancer in front of Artifactory caps request body size (client_max_body_size) below the artifact size.

A large single-request upload

A very large artifact sent in one request exceeds the platform or proxy maximum for that path.

How to fix it

Raise the proxy body-size limit

Increase the reverse proxy maximum body size so large artifacts pass through to Artifactory.

nginx.conf

# nginx in front of Artifactory
client_max_body_size 5000m;

Use chunked upload for large files

The jf CLI can split large uploads so no single request exceeds the limit.

Terminal

jf rt upload "build/large-artifact.tar" libs-release-local/ --split-count=5 --min-split=100

How to prevent it

Set the proxy body-size limit above your largest artifact.
Use chunked or split uploads for very large files.
Watch for HTML 413 pages that signal a proxy, not Artifactory, limit.