Proget package upload size limit

morten.thorsen_4871

Is there any way to get around the rather limiting 2GB package size for uploads of universal packages in the self-hosted version of Proget?

I seems kinda stupid to be subject to such a limit in 2019 where we can easily up and download (stream) much more data via HTTP(S).

atripp

Hello;

You can edit the web.config file with the following changes to allow for bigger uploads;

<httpRuntime requestValidationMode="2.0" requestPathInvalidCharacters="" maxRequestLength="2147483647" executionTimeout="86400" targetFramework="4.5" />

<requestLimits maxAllowedContentLength="4294967295" maxQueryString="1048576" maxUrl="1048576" />

morten.thorsen_4871

@atripp said in Proget package upload size limit:

4294967295

That looks very much like the max value of a an uint. Can we go beyond that?

atripp

I'm afraid not; these are the maximum values the platform (.NET for one, IIS for the other) supports. We may add chunking support for universal packages in the future (like we do for asset directories), but until then your best work-around is to use the drop-path import.

morten.thorsen_4871

@atripp I'm not sure why you are limited by this, when not using IIS.

I made a small ASP web API test, that can receive any size package (probably 2^64 bytes) streaming without using any memory.
This is as self-hosted, I guess using Katana.

Any reason you can't do this?

atripp

I'm not really sure either, but the exception (request length exceeded, etc) always been coming from the platform, regardless of how it's hosted (IIS error or .NET error). If we remove the config values then it defaults to a really low value like 2MB or something. Maybe it's .NET452 that we're using? I don't know.

There may be a way around it, but we haven't invested engineering resources in exploring it because there's virtually no demand for this. Nearly all customers prefer IIS for installations, and those who are OK with our web server don't have large packages.

It might be trivial and low risk, and you're more than welcome to explore (whether editing configs or looking through source code) -- and if so we'll gladly incorporate the change.

morten.thorsen_4871

@atripp I have requested source code access, but haven't heard anything yet. Can you accelerate?

atripp

You should have access now! Let me know if not :)