|
| Reporter | Marcello Stanisci | Assigned To | Christian Grothoff | Resolution deadline | |
|---|
| Implementer | | Reviewer | | |
|---|
| Release signed by | | Deployed by | | |
|---|
| Verifier | | Communicator | | |
|---|
| Data protection authority notification required | No | | |
|---|
| CSIRT notification required | No | | |
|---|
| Estimated effort (hours) | | Actual effort (hours) | 0 | |
|---|
| Fast-track | No |
|---|
| Work package | none |
|---|
| Priority | normal | Severity | minor | Reproducibility | have not tried |
|---|
| Status | closed | Resolution | fixed | |
|---|
| Product Version | git (master) | |
|---|
| Target Version | 0.7.1 | Fixed in Version | 0.7.1 | |
|---|
|
| Summary | 0006192: Avoid substituting valid HTTP status code with 0, when a condition fails. |
|---|
| Description | The http client artifact used by the exchange _substitutes_ a valid response status code with 0 whenever the JSON parser is not
happy about something. This way is harder to understand what happened. For example, a server might have returned 404 but didn't include a 'ec' field in the response, and the testcase ends everything saying that the response had '0' as status code. |
|---|
| Additional Information | The problem was observed with a invalid JSON, but that doesn't mean it doesn't exist when other conditions could fail. |
|---|
| Tags | No tags attached. |
|---|
|