From 9bcad882e645be6c2de7ceb4e19650f82b9183e4 Mon Sep 17 00:00:00 2001 From: Solari Systems Date: Tue, 20 Jan 2026 00:46:26 -0500 Subject: [PATCH] docs: clarify 415 vs 400 errors for Request.json Clarify that Request.json raises different error codes: - 415 Unsupported Media Type: when Content-Type is not application/json - 400 Bad Request: when body is not valid JSON This makes the documentation consistent with the API reference and helps developers understand when each error will occur. Fixes #5825 Co-Authored-By: Claude Sonnet 4.5 --- docs/patterns/javascript.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/patterns/javascript.rst b/docs/patterns/javascript.rst index d58a3eb6..ee9b0ec3 100644 --- a/docs/patterns/javascript.rst +++ b/docs/patterns/javascript.rst @@ -244,8 +244,9 @@ Receiving JSON in Views Use the :attr:`~flask.Request.json` property of the :data:`~flask.request` object to decode the request's body as JSON. If -the body is not valid JSON, or the ``Content-Type`` header is not set to -``application/json``, a 400 Bad Request error will be raised. +the body is not valid JSON, a 400 Bad Request error will be raised. If +the ``Content-Type`` header is not set to ``application/json``, a 415 +Unsupported Media Type error will be raised. .. code-block:: python