Better HTTP Status Code for Empty Requests

[mbbyn]

System Info

(I don't think it's necessary)

Information

• Docker
• The CLI directly

Tasks

• An officially supported command
• My own modifications

Reproduction

Expected behavior

HTTP status 400 is more appropriate IMHO. The 413 status code might lead to misinterpretation. For example, when integrated with Dify, dify translates the 413 to Payload too large, but there is not payload to begin with.

[mbbyn]

Related langgenius/dify#6807

[OlivierDehaene]

The 413 status code is causing red-herring, wild goose-chase, witch-hunting, etc.

???

[mbbyn]

Hey @OlivierDehaene, could you please elaborate as to what's the issue with the description? I hope it's nothing offensive, as I was just trying to describe it in a light-hearted manner. If that's not the interpretation, I apologize and can edit it to be more formal.

[eero-t]

@OlivierDehaene The returned 413 error for too large requests: https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#4xx_client_errors

Besides it being incorrect one for empty requests, it makes finding the actual issue harder (e.g. if one has large cluster with large number of requests flying around, and that error code only bubbles up to some higher level report).

[OlivierDehaene]

@mbbyn, well it's a strange way to introduce yourself to a complete stranger.
@eero-t, I guess? But at the same time the payload of the error was inputs cannot be empty which makes it pretty obvious to the caller what they need to check...

In any case, #413 uses a 400 instead.