After upgrading from 5.4.4 to 5.10.4, the user will experience issues downloading large files (>1GB). They get returned from curl:
*curl -L -o again.txt -G http://myserver/artifactory/example-repo-local/test.txt*
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
67 1524M 67 1032M 0 0 3785k 0 0:06:52 0:04:39 0:02:13 1430k
curl: (18) transfer closed with 515411771 bytes remaining to read
It will always close around the 1GB mark. The request logs return a 200 and display the correct size of the file. The artifactory logs show a 499:
[WARN ] (o.a.r.ArtifactoryResponseBase:137) - Client Closed Request 499: java.net.SocketTimeoutException
Reproduce
- start up a 5.4.4 instance
- Setup nginx proxy with Artifactory generated config
- deploy a 1.5 GB file
- try to download with curl (curl -L -o again.txt -G http://myserver/artifactory/example-repo-local/test.txt)
- **download will succeed
- upgrade to 5.10.4
- download once again to see error and failed download
Workaround
add the proxy_max_temp_file_size to nginx configuration and set to 0 or some larger amount. Its default value is 1024 (1GB)
We would like to know what would have changed in the upgrade process that would need the addition of this property in nginx for large files.
- is cloned by
-
RTFACT-27198 CLONE - Issue with nginx configuration on large file downloads
- Open