pgadmin-org / pgadmin-org/pgadmin4
Support more gunicorn configurations via env vars
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.8k
- Forks
- 891
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 8
Description
Describe the solution you'd like
Currently only some gunicorn configurations are supported. Currently we are seeing errors with using pgadmin if our authorization bearer token exceed a specific size. We are using JWT with many informations inside and quickly checking a single token it exceeds the default 8190 bytes like described here: https://docs.gunicorn.org/en/stable/settings.html#limit-request-field-size
We would need to adjust this field for our use case.
We especially need able to configure the gunicorn config: limit-request-field-size
Describe alternatives you've considered
Additional context
Related error: https://www.itsfullofstars.de/2022/02/apache-ah00561-size-of-a-request-header-field-exceeds-server-limit/
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how pgAdmin's existing Gunicorn settings are exposed through environment variables. Check the Gunicorn setting documentation for limit-request-field-size and reproduce the oversized JWT request described in the issue. Done means this setting can be configured through the supported environment-variable mechanism and the request no longer fails at the default limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100