[
https://issues.apache.org/jira/browse/OFBIZ-13278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18014310#comment-18014310
]
Jacques Le Roux commented on OFBIZ-13278:
-----------------------------------------
BTW, I just tried using [https://demo-stable.ofbiz.apache.org/rest/auth/token]
several times, I always get:
{
"statusCode" : 405,
"statusDescription" : "Method Not Allowed",
"errorMessage" : "HTTP 405 Method Not Allowed"
}
It's maybe a special case?
> Repeated REST API exception results in generic 500 error instead of specific
> response
> -------------------------------------------------------------------------------------
>
> Key: OFBIZ-13278
> URL: https://issues.apache.org/jira/browse/OFBIZ-13278
> Project: OFBiz
> Issue Type: Bug
> Components: rest-api
> Affects Versions: 24.09.02
> Reporter: Arashpreet Singh
> Priority: Major
>
> When a REST API exposed via the {{rest-api}} module is called and an
> exception occurs during execution, OFBiz initially returns an appropriate
> error response. However, if the same API is called again and the exception
> persists, OFBiz returns a generic HTTP 500 Internal Server Error without
> providing the specific error message or exception details that were returned
> on the first call.
> *Steps to Reproduce:*
> # Call a REST API (e.g., {{{}/rest/some-endpoint{}}}) that is expected to
> raise an exception due to missing input, business logic failure, or invalid
> state.
> # Observe the first response – it contains a descriptive error message.
> # Without fixing the root cause, call the same API again.
> # The second response returns HTTP 500 Internal Server Error without the
> original error message.
> *Expected Behavior:*
> * The API should return a consistent and descriptive error response each
> time the same exception occurs, not a generic 500 error.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
