Malformed curl command causes internal error
Bug #1367888 reported by
Tim Hinrichs
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| congress |
Fix Released
|
Medium
|
Peter Balland | ||
Bug Description
When someone uses curl to issue API commands to Congress, malformed JSON in the body of the HTTP message causes an Internal server error instead of an error indicating the request was malformed.
| Changed in congress: | |
| importance: | Undecided → Medium |
| assignee: | nobody → Peter Balland (pballand) |
Revision history for this message
| Peter Balland (pballand) wrote | #1 |
| Changed in congress: | |
| status: | New → Triaged |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to congress (master) | #2 |
| Changed in congress: | |
| status: | Triaged → In Progress |
| Changed in congress: | |
| status: | In Progress → Fix Committed |
| Changed in congress: | |
| milestone: | none → liberty-2 |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This is caused by an uncaught exception from the JSON parser. This should be caught by the validation framework (along with valid JSON with incorrect data), but I can put in a quick catch to handle invalid JSON in the mean time.