Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[dev.icinga.com #11757] API: Missing error handling for invalid JSON request body #4202

Closed
icinga-migration opened this issue May 10, 2016 · 1 comment
Labels
area/api REST API bug Something isn't working
Milestone

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/11757

Created by mfriedrich on 2016-05-10 13:12:58 +00:00

Assignee: mfriedrich
Status: Resolved (closed on 2016-05-10 13:20:03 +00:00)
Target Version: 2.4.8
Last Update: 2016-05-10 13:20:03 +00:00 (in Redmine)

Icinga Version: 2.4.7
Backport?: Not yet backported
Include in Changelog: 1

Right now this causes a plain-text exception message.

Example for a check command with an invalid json body.

{
  "templates": [
    "plugin-check-command"
  ]
  "attrs": {
    "command": [
      "/bin/echo"
    ]
  }
}

i2_api_invalid_json.png

Attachments

Changesets

2016-05-10 13:16:35 +00:00 by mfriedrich 9a88185

API: Fix error handling for invalid JSON request body

fixes #11757

2016-05-12 09:09:49 +00:00 by mfriedrich 7f915db

API: Fix error handling for invalid JSON request body

fixes #11757
@icinga-migration
Copy link
Author

Updated by mfriedrich on 2016-05-10 13:20:03 +00:00

  • Status changed from Assigned to Resolved
  • Done % changed from 0 to 100

Applied in changeset 9a88185.

@icinga-migration icinga-migration added bug Something isn't working area/api REST API labels Jan 17, 2017
@icinga-migration icinga-migration added this to the 2.4.8 milestone Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/api REST API bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant