Wrong encoded URL query

Status #

400

Meaning #

The API responds with ‘Wrong encoded URL query’ if you’ve executed a GET request against the route …

• /hybrid-core/v1/sites
• /hybrid-core/v1/sites/:site_id/assets

with wrong encoded query string. Finally, you get that response, if you’ve passed the query encoded to request respective route, but the encoding doesn’t match to any valid HTML encoding.

Semantically the response status code is equivalent to the HTTP 400 Bad Request response status code. It indicates that the server can’t process your request as well as that a part of the request you’ve send doesn’t fit the defined format in any manner.

On the one hand the 400 error is an error which is interpreted as a server-side problem. On the other hand, from the technical view the error belongs to a client-side issue, because at the moment when the request is fired by the client he should be aware about the encoding he chooses to pass the query he is using for GET request against given route. This is the reason why this type of error is categorized within the scope of client-side (4xx) responses.

Request #

GET https://api.gridscale.io/hybrid-core/v1/sites?sort%ßid%5D=-

Response #

Header:

HTTP/1.1 400 Bad Request
Content-Type: application/json; charset=utf-8
...

Body:

{
  "errors": [
    {
      "type": "https://my.gridscale.io/docs/apis/problems/hybrid-core/v1/wrong-encoded-url-query",
      "title": "Wrong encoded URL query",
      "status": 400,
      "detail": "Requested URL query string is wrong encoded.",
      "DocURL": "https://my.gridscale.io/docs/apis/hybrid-core/v1/introduction",
    }
  ]
}