Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • POD POD
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 57
    • Issues 57
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 10
    • Merge requests 10
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • MemriMemri
  • PODPOD
  • Issues
  • #411
Closed
Open
Issue created Sep 21, 2021 by Vasili Novikov@vasiliContributor

Give better HTTP Responses for ContentLength limits

Currently, Pod will respond 404 Not Found for requests which body exceeds a certain value (currently 5 Mb). This is confusing for a developer that develops against this API.

Instead, Pod should be changed to respond with 400 Bad Request https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#4xx_client_errors and specify the reason of the failure in the response body (any short description will do).

┆Issue is synchronized with this Clickup task by Unito

Edited Feb 09, 2022 by Aglaia
Assignee
Assign to
Time tracking