ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Belyak (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-6750) Return "wrong command" error in http rest api
Date Wed, 25 Oct 2017 10:32:01 GMT
Alexander Belyak created IGNITE-6750:
----------------------------------------

             Summary: Return "wrong command" error in http rest api
                 Key: IGNITE-6750
                 URL: https://issues.apache.org/jira/browse/IGNITE-6750
             Project: Ignite
          Issue Type: Bug
      Security Level: Public (Viewable by anyone)
          Components: general
    Affects Versions: 2.2, 2.1, 2.0, 1.9
            Reporter: Alexander Belyak
            Priority: Minor
             Fix For: 2.4


If I make mistake in command name, for example

curl "http://localhost:8080/ignite?cmd=wrongcmd"

<no output here>

I get no error message and nothing will be logged in ignite log (even in IGNITE_QUIET=false
mode) and only by getting response code

curl -I "http://localhost:8080/ignite?cmd=wrongcmd"

HTTP/1.1 400 Bad Request
Date: Wed, 25 Oct 2017 10:03:06 GMT
Content-Type: application/json; charset=UTF-8
Content-Length: 0
Server: Jetty(9.2.11.v20150529)

I can see something, but without root cause.
We need:
1) return error text

curl "http://localhost:8080/ignite?cmd=wrongcmd"

{"successStatus":1,"sessionToken":null,"error":"Failed to handle request: [req=UNKNOWN, err=Failed
to find command: wrongcmd]","response":null}

 as usual:

curl "http://localhost:8080/ignite?cmd=get"

{"successStatus":1,"sessionToken":null,"error":"Failed to handle request: [req=CACHE_GET,
err=Failed to find mandatory parameter in request: key]","response":null}

2)  set status code in http response to 400 ( http://www.restapitutorial.com/httpstatuscodes.html
)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message