lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cassandra Targett (JIRA)" <>
Subject [jira] [Updated] (SOLR-7312) "REST" API is not REST
Date Thu, 20 Jul 2017 19:24:00 GMT


Cassandra Targett updated SOLR-7312:
    Component/s: documentation

> "REST" API is not REST
> ----------------------
>                 Key: SOLR-7312
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>          Components: documentation, Server
>    Affects Versions: 5.0
>            Reporter: Mark Haase
>            Assignee: Noble Paul
> The documentation refers to a "REST" API over and over, and yet I don't see a REST API.
I see an HTTP API but not a REST API. Here are a few things the HTTP API does that are not
> * Offers RPC verbs instead of resources/nouns. (E.g. schema API has commands like "add-field",
"add-copy-field", etc.)
> * Tunnels non-idempotent requests (like creating a core) through idempotent HTTP verb
> * Tunnels deletes through HTTP GET.
> * PUT/POST confusion, POST used to update a named resource, such as the Blob API.
> * Returns `200 OK` HTTP code even when the command fails. (Try adding a field to your
schema that already exists. You get `200 OK` and an error message hidden in the payload. Try
calling a collections API when you're using non-cloud mode: `200 OK` and an error message
in the payload. Gah.)
> * Does not provide link relations.
> * HTTP status line contains a JSON payload (!) and no 'Content-Type' header for some
failed commands, like `curl -X DELETE http://solr:8983/solr/admin/cores/foo`
> * Content negotiation is done via query parameter (`wt=json`), instead of `Accept` header.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message