You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@fineract.apache.org by "Robert Jakech (Jira)" <ji...@apache.org> on 2022/11/03 11:44:00 UTC

[jira] [Updated] (FINERACT-1243) Invalid dateFormat should return validation (400) instead of internal server error (500) HTTP response

     [ https://issues.apache.org/jira/browse/FINERACT-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Jakech updated FINERACT-1243:
------------------------------------
    Labels: Roadmap2022  (was: )

> Invalid dateFormat should return validation (400) instead of internal server error (500) HTTP response
> ------------------------------------------------------------------------------------------------------
>
>                 Key: FINERACT-1243
>                 URL: https://issues.apache.org/jira/browse/FINERACT-1243
>             Project: Apache Fineract
>          Issue Type: Improvement
>            Reporter: Michael Vorburger
>            Priority: Major
>              Labels: Roadmap2022
>
> An invalid {{dateFormat}} sent by a client, such as the {{yyyy-mm-dd}} instead of {{yyyy-MM-dd}} seen in FINERACT-1242, should "just" return an invalid client request validation error (HTTP response code 400) instead of cause an internal server error with error log on the server side and 500 response.
> This is in line with our https://github.com/apache/fineract/#logging-guidelines.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)