Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
I'm working on a system where the frontend will make a call to the backend to perform an action. Sometimes this action can cause other unintended consequences (like charging the customer), in thes...
#3: Post edited
by
Welz
·
2022-01-12T17:08:25Z (almost 3 years ago)
What would be an appropriate HTTP status code for "confirmation required"
- Appropriate HTTP status code for "user confirmation required"
#2: Post edited
by
Welz
·
2022-01-12T17:01:21Z (almost 3 years ago)
What would be an appropriate HTTP status code for "further information"
- What would be an appropriate HTTP status code for "confirmation required"
#1: Initial revision
by
Welz
·
2022-01-12T17:01:04Z (almost 3 years ago)
What would be an appropriate HTTP status code for "further information"
I'm working on a system where the frontend will make a call to the backend to perform an action. Sometimes this action can cause other unintended consequences (like charging the customer), in these circumstances I want the backend to respond with a status code indicating > What you did is fine, just make sure that's what you want to do because it will do XYZ Essentially if the frontend got this response it just means prompt the user to confirm the changes and submit the request again (perhaps with different attributes based on their selection). In most cases we don't need a confirmation, that's why I don't want to implement it on all requests. There are specific circumstances that require an extra layer of confirmation (and once confirmed the request can proceed as usual or slightly differently depending on what the user selected). --- I'd like to know if there's a specific response code that would be appropriate to give to the frontend to indicate that further action is required. The best one I could come up with was **[202 Accepted](https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.2.3)**, though I'm not sure it's correct based on what I described above.