[CONTROLLER-750] JSON response for non matching endtag with header containing accept application/xml Created: 01/Sep/14 Updated: 25/Jul/23 Resolved: 17/Sep/14 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | restconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | RichardHill | Assignee: | Jozef Gloncak |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: Windows |
||
| External issue ID: | 1659 |
| Description |
|
When making the request below a JSON response was received when a XML format was expected. Adding a flow with a non matching end tag. 'method': 'POST', , RECEIVED {'errors': {'error': {'error-type': 'protocol', 'error-tag': 'malformed-message', 'error-message': 'error parsing input: parseerror at [row,col]:[7,3]\nmessage: the element type "instructions" must be terminated by the matching end-tag "</instructions>".'}}} TEST ENV org.opendaylight.controller.version = 0.1 STEPS |
| Comments |
| Comment by Tony Tkacik [ 08/Sep/14 ] |
|
Please provide steps to reproduce, since I was unable to reproduce it using Postman and request you provided. |
| Comment by Tony Tkacik [ 09/Sep/14 ] |
|
Could not replicate on current master and 1 week old master. |
| Comment by RichardHill [ 12/Sep/14 ] |
|
As you discussed later this was due to postman sanitising the HTTP headers so reopening the bug. |
| Comment by Jozef Gloncak [ 16/Sep/14 ] |
|
patch set Returning value (errors or data) will be by default in JSON format. |