GitHub

request.malformed

The request cannot be read: invalid JSON, the wrong content type

Profile

Errors

Raised with

fail()

Status

400

Message

yours
View as Markdown

Request intents

Example

TS
return fail('request.malformed', 'Invalid JSON.');
The caller gets
Terminal
HTTP 400

{
  "ok": false,
  "error": "Invalid JSON.",
  "code": "request.malformed"
}

Choosing between neighbours

Find the row that describes your case, and use the intent on the right.

  • If it is

    Use

  • The request cannot be read: invalid JSON, the wrong content type

    request.malformed this page

  • A readable request with a wrong value

    request.invalid

Connections

Declared in the registry, both directions. Where an intent is used in your own code is something check and the gallery see; this site has no app code.

For registry authors

Starter intents. These are the intents prongs add errors puts in your registry, raised with fail(). Change the messages to suit your app, and the statuses through the status.* intents they are built from.

The entry prongs add errors writes into your registry. Change the message here, or the status through its status.* ref.

TS
'request.malformed': {
  kind: 'semantic',
  description: 'The request cannot be read: invalid JSON, the wrong content type',
  refs: ['status.badrequest'],
  keywords: ['json', 'parse', 'malformed'],
  notFor: [
    {
      context: 'a readable request with a wrong value',
      instead: 'request.invalid',
    },
  ],
  binding: { publicMessage: 'Invalid request.' },
},