[
https://issues.apache.org/jira/browse/SOLR-18439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated SOLR-18439:
----------------------------------
Labels: pull-request-available (was: )
> Some v2 "command" APIs report failures via HTTP 200 instead of a proper
> 4xx/5xx status
> --------------------------------------------------------------------------------------
>
> Key: SOLR-18439
> URL: https://issues.apache.org/jira/browse/SOLR-18439
> Project: Solr
> Issue Type: Improvement
> Components: v2 API
> Reporter: Eric Pugh
> Assignee: Eric Pugh
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Solr's v2 API conventions (dev-docs/v2-api-conventions.adoc, "Errors"
> section) require that a failure be reported by throwing a SolrException,
> which the shared CatchAllExceptionMapper converts into the correct HTTP
> status code plus error.code/error.msg in the body. A few v2 endpoints bypass
> this — they catch the failure themselves, stuff it into a custom field on the
> response object, and return normally, so the client sees HTTP 200 for a real
> failure.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
