Bug: Error 502 Bad Gateway on large requests for file invalidation server
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7
- Forks
- 34
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 3
Description
Bug Description
The file invalidation server will show a 502 Bad gateway when a request is sent with a large number of files (~ >800). The invalidation request is correctly generated after a few minutes according to the container logs but this leaves the user clueless.
Reproduction Steps
- Send a large request (>1000 files) to https://file-invalidation.app.cern.ch/api/upload/ in dry_run_mode
- After a while loading the screen will show 502 Bad gateway error
Expected Behavior
Show a specific error message to the user if needed.
Possible Solution
Handle the post request in batches or use a loading page.
Related Issues
No response
Contributor guide
No contributing guide indexed for this repository
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
Reproduce the issue by sending more than 1,000 files to https://file-invalidation.app.cern.ch/api/upload/ in dry_run_mode, then compare the client response with the container logs showing the invalidation completes. Trace the upload endpoint and its request handling to determine where the 502 is generated. Done means large requests provide a useful user-visible result instead of an unexplained 502.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100