search

snipe / snipe-it

A free open source IT asset/license management system
https://snipeitapp.com
GNU Affero General Public License v3.0
11.21k stars 3.2k forks source link

Cookie Size gets too big due to Column Customization, results in Bad Request (Docker Setup) #15917

Open user-4711 opened 17 hours ago

user-4711 commented 17 hours ago

Debug mode

Describe the bug

After hiding multiple columns in Assets, Licenses, People, the People page can't be opened anymore and the apache reports the following:

Your browser sent a request that this server could not understand.
Size of a request header field exceeds server limit.

After adding LimitRequestFieldSize 200000 to /etc/apache2/sites-enabled/000-default.conf and restarting the apache service, everything works as expected.

Reproduction steps

  1. Open Assets, hide multiple columns
  2. Open Licenses and hide multiple Columns
  3. Open People and hide multiple Colums
  4. Refresh the Browser ... I couldn't reproduce the issue in the demo, probably due to different apache settings.

Expected behavior

The People page should be shown with my customized column settings

Screenshots

No response

Snipe-IT Version

7.1.15

Operating System

Ubuntu (Docker)

Web Server

Apache (Docker)

PHP Version

8.1 (Docker)

Operating System

Windows

Browser

Chromium / Firefox / Edge

Version

latest

Device

No response

Operating System

No response

Browser

No response

Version

No response

Error messages

No response

Additional context

The installation is a migrated instance from a Debian Host to a Docker Container. On the Debian Host we just added a line to the site-config and that also works in the docker container, but it's not a permanent solution. I tried to pass LimitRequestFieldSize as a variable to the instance like i did with PHP_UPLOAD_LIMIT, but I couldn't figure it out. I'm not a docker guru.

I'd like to see the a higher default value in the Docker Image for LimitRequestFieldSize.

Cheers!

welcome[bot] commented 17 hours ago

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.