Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃悰 Bug: API V2 "Offset is beyond the total number of records" error status code returned is 200 instead of 400 #7367

Closed
1 task done
woodmin opened this issue Jan 4, 2024 · 1 comment
Assignees
Labels
Status: Reproducible Able to reproduce the issue based on the reporters' guideline.

Comments

@woodmin
Copy link

woodmin commented Jan 4, 2024

Please confirm if bug report does NOT exists already ?

  • I confirm there is no existing issue for this

Steps to reproduce ?

Set API Call offset > the total number of records.
API response body contains: {"message":"Offset is beyond the total number of records"}
Status returned is 200 (Success) instead of 400 (Bad request).

Desired Behavior

Status returned on "Offset is beyond the total number of records" should be 400 (Bad request).

Project Details

Node: v18.18.2
Arch: x64
Platform: linux
Docker: true
RootDB: pg
PackageVersion: 0.203.2
Database version : 16.1

Attachments

No response

@woodmin
Copy link
Author

woodmin commented Jan 4, 2024

I have reported other API Error Message / Status mismatches before. Could it be also checked along in the code if any more errors (messages) are not set to be returned with 200 status? For example: Invalid URL Format, Missing Required Parameters, Request Size Too Large, etc.?

@dstala dstala added the Status: Reproducible Able to reproduce the issue based on the reporters' guideline. label Jan 5, 2024
@dstala dstala added this to the vNext milestone Jan 5, 2024
@dstala dstala closed this as completed Jan 11, 2024
@dstala dstala removed this from the vNext milestone Jan 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Reproducible Able to reproduce the issue based on the reporters' guideline.
Projects
None yet
Development

No branches or pull requests

3 participants