File upload via Gitlab UI does not enforce maximum attachment size on Gitlab self-hosted

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Summary

On Gitlab (CE) self hosted, files larger than the configured maximum attachment size can be uploaded. Push limits are properly enforced.

Steps to reproduce

1. Run Gitlab (CE) 17.6.2 self hosted in docker

2. Configure maximum attachment size in the Admin panel to 50 MiB

   

3. Use the Gitlab UI to upload a file larger than 50 MiB

4. Upload proceeds without issue

   

Example Project

This bug does not occur on Gitlab.com (I tested it just now).

What is the current bug behavior?

Files that are larger than the maximum attachment size are uploaded.

What is the expected correct behavior?

File upload should stop with an error message if the file is too large.

Relevant logs and/or screenshots

See screenshots in Steps to reproduce.

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)
(we will only investigate if the tests are passing)

Possible fixes