[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["必要な情報がない","missingTheInformationINeed","thumb-down"],["複雑すぎる / 手順が多すぎる","tooComplicatedTooManySteps","thumb-down"],["最新ではない","outOfDate","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["サンプル / コードに問題がある","samplesCodeIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-07-25 UTC。"],[[["\u003cp\u003eKACLS operation failures now return structured JSON responses for improved debugging.\u003c/p\u003e\n"],["\u003cp\u003eThese JSON responses include an HTTP status code, a human-readable message, and detailed error information.\u003c/p\u003e\n"],["\u003cp\u003eThis structure facilitates easier integration with automated systems and provides developers with more context for troubleshooting.\u003c/p\u003e\n"]]],["KACLS operation failures now return a structured JSON response in the body, using standard HTTP status codes. The JSON format includes three fields: `code` (an integer representing the HTTP status), `message` (a human-readable error string), and `details` (a string providing further information like a stack trace). This structured format improves the quality of error messages and logs.\n"],null,["# Structured error replies\n\nTo allow better messages and logs, the Key Access Control List Service (KACLS)\noperation failures returns a structured JSON reply in the body.\nThe standard HTTP status codes are used.\n\n| JSON representation ||\n|---------------------------------------------------------------|---|\n| ``` { \"code\": int, \"message\": string, \"details\": string } ``` |\n\n| Fields ||\n|-----------|-----------------------------------------------------------------------|\n| `code` | `int` Standard HTTP status code |\n| `message` | `string (UTF-8)` A human readable error message. |\n| `details` | `string (UTF-8)` More details about the error, such as a stack trace. |"]]