Large (>4GiB) package uploads fail with 413 Request Entity Too Large

[rob.leadbeater_2457]

Hi,

I'm trying to upload a large (bigger than 4GiB) Universal Package to a feed using curl, which is failing with the following error.

> PUT /upack/test-feed HTTP/1.1
> Host: proget.internal:8624
> Authorization: Basic xxxxx
> User-Agent: curl/7.74.0
> Accept: */*
> Content-Length: 4404364110
> Expect: 100-continue
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 413 Request Entity Too Large
< Content-Type: text/html
< Server: Microsoft-IIS/10.0
< X-Powered-By: ASP.NET
< Date: Tue, 22 Nov 2022 10:48:04 GMT
< Connection: close
< Content-Length: 67
<
* Closing connection 0
The page was not displayed because the request entity is too large.

From previous forum posts, this looks like it could be down to an IIS configuration setting, but nothing I've changed seems to have had any effect. I'm assuming a value of 0 should remove the limit.

system.web/httpRuntime/maxRequestLength = 0
system.webServer/serverRuntime/maxRequestEntityAllowed = 0

• ProGet version 2022.14
• IIS v10

I can see that the asset directory API has a multipart upload feature. Is there an equivalent for uploading to feeds?

Cheers,
Rob

[atripp]

Hi @rob-leadbeater_2457 ,

This is a "hard-coded" limit that's built into IIS I'm afraid; if you use the built-in Web Server or Docker, this is not an issue. Another option is to use a drop-path for the packages.

Otherwise, we have not implemented multi-part / chunked upload for Universal Packages yet; it's on our list, but there's not a huge demand for it.

Cheers,
Alana