This repository was archived by the owner on Nov 24, 2025. It is now read-only.
return correct error on duplicate email while updating user #7394
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.
Closes: #7249
Currently, a user updating their email to one that's already in use returns an
500 Internal Server Error. This PR updates the implementation to ensure that a400 Bad Requesterror with a description is returned instead.Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
POST /usersendpoint)PUT /user/currentendpoint)If this is a bugfix, which Traffic Control versions contained the bug?
Wasn't able to track down the exact release where this bug originated. This bug is present in
masterbranch & #3996 is the PR where the endpoint was first written for API V3.PR submission checklist
PR doesn't need any separate documentation since only the error handling behaviour has been changed. API docs only document the request & response structure.