annotate website/issues/TEMPLATE-INFO.txt @ 6311:be8d5a8e090a

Fix uncaught error when parsing rest headers, document Started this work as better docs for rest response format. But I found 406 error response was not being tested. Also there was no error for bad Content-Type. In rest.py fix uncaught exceptions due to invalid Accept or Content-Type headers. If Content-type is valid but not application/json return code 415. Document use of accept header (was only shown in examples) and support for q parameter. Describe using .xml and .json extensions to select return format for testing from browser (where setting accept header is a problem). Document 406 error code return. Document 415 error code return and acceptable content types. Previously only doc was in examples. Set up tests for 406 and 415 error codes.
author John Rouillard <rouilj@ieee.org>
date Fri, 01 Jan 2021 14:14:34 -0500
parents 40329ed1cced
children
Ignore whitespace changes - Everywhere: Within whitespace: At end of lines:
rev   line source
6105
40329ed1cced add mising template info so it can be used as a template
John Rouillard <rouilj@ieee.org>
parents:
diff changeset
1 Name: issue
40329ed1cced add mising template info so it can be used as a template
John Rouillard <rouilj@ieee.org>
parents:
diff changeset
2 Description: this is the issue tracker for roundup.
40329ed1cced add mising template info so it can be used as a template
John Rouillard <rouilj@ieee.org>
parents:
diff changeset
3 Intended-For: production use by roundup.
40329ed1cced add mising template info so it can be used as a template
John Rouillard <rouilj@ieee.org>
parents:
diff changeset
4

Roundup Issue Tracker: http://roundup-tracker.org/