[
https://issues.apache.org/jira/browse/IGNITE-23421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vadim Pakhnushev updated IGNITE-23421:
--------------------------------------
Description:
When cluster is not yet initialized (or in the process of initialization), any
URL that is not found responds with http code 409 and message "Cluster is not
initialized" instead of code 404 and message "Page not found".
This happens because we handle "not found" errors using special controller
{{GeneralErrorsController}}. When Micronaut can't find the controller for the
incoming request, it uses this controller to handle the error, but before that
it uses the {{ClusterStateHttpServerFilter}} which checks the path availability
using a list of available endpoints, meaning that any endpoint which is not in
that list leads to the 409 response from this filter.
We might change the availability check to use the list of unavailable endpoints
but this needs to be tested well so that the new endpoint won't be forgotten to
be included in this list.
was:
When cluster is not yet initialized (or in the process of initialization), any
URL that is not found responds with http code 409 and message "Cluster is not
initialized" instead of code 404 and message "Page not found".
This happens because we handle "not found" errors using special controller
{{GeneralErrorsController}}. When Micronaut can't find the controller for the
incoming request, it uses this controller to handle the error, but before that
it uses the {{ClusterStateHttpServerFilter}} which checks the path availability
using closed list of available endpoints, meaning that any endpoint which is
not in that list leads to the 409 response from this filter.
> Not found URLs respond with 409 instead of 404
> ----------------------------------------------
>
> Key: IGNITE-23421
> URL: https://issues.apache.org/jira/browse/IGNITE-23421
> Project: Ignite
> Issue Type: Bug
> Components: rest
> Reporter: Vadim Pakhnushev
> Priority: Major
> Labels: ignite-3
>
> When cluster is not yet initialized (or in the process of initialization),
> any URL that is not found responds with http code 409 and message "Cluster is
> not initialized" instead of code 404 and message "Page not found".
> This happens because we handle "not found" errors using special controller
> {{GeneralErrorsController}}. When Micronaut can't find the controller for the
> incoming request, it uses this controller to handle the error, but before
> that it uses the {{ClusterStateHttpServerFilter}} which checks the path
> availability using a list of available endpoints, meaning that any endpoint
> which is not in that list leads to the 409 response from this filter.
> We might change the availability check to use the list of unavailable
> endpoints but this needs to be tested well so that the new endpoint won't be
> forgotten to be included in this list.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
