🐛 [REST API] Respond with 403
when max allowed limit for entities is exceeded
#4154
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This pull request fixes an issue where exceeding the maximum allowed limit for entities resulted in the server returning an incorrect HTTP 500 (Internal Server Error) response. The behavior is now updated to return the correct HTTP 403 (Forbidden) status code when such limits are exceeded, as per service expectations.
Changes
KapuaMaxNumberOfItemsReachedException
to ensure it maps to a 403 status code instead of 500.entityType
) for better traceability and debugging.Why this is important
The previous 500 response indicated a server-side error, which led to confusion and misalignment with the intended service behavior. These changes ensure that exceeding service-defined limits is appropriately flagged as a client-side issue (403 Forbidden), improving correctness and reliability of APIs.
How to reproduce the original issue
Expected Behavior After Fix