Change HTTP Response Code to 400 Bad Request for Parse Errors

Why it matters

This feature improves HTTP API error handling by returning a more specific and appropriate response code (400 Bad Request) when the server encounters parse errors in client requests. This helps users and clients better identify client-side request issues instead of generic server errors.

How to use it

No special activation is needed. The HTTP API now automatically returns a 400 Bad Request response code for relevant parse errors.