A legacy inspection API returns HTTP 200 with an error string in the body. Mobile clients need proper 4xx/5xx status codes and a cleaned JSON shape without rewriting every backend method yet. What should developers use?
Select an answer to reveal the explanation.
Short Explanation
The old inspection API smiles with a 200 while whispering "error" in the body — mobile apps hate that. Use API Gateway mapping or response overrides to fix the status and JSON at the edge. You get cleaner clients without rewriting every backend method today.
Full Explanation
API Gateway supports integration response mapping and status overrides so edge clients receive correct HTTP semantics and reshaped JSON while legacy backends catch up. Teaching every client to parse error strings in 200 bodies is fragile. CloudFront caching does not generally rewrite application error semantics, and WAF is for filtering threats—not normalizing API contracts.