Mercurial > p > roundup > code
view MANIFEST.in @ 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 | a635a60ffb84 |
| children | b3ba03d2b214 |
line wrap: on
line source
recursive-include share * recursive-include roundup *.* recursive-include frontends *.* recursive-include scripts *.* *-* recursive-include tools *.* base64 recursive-include test *.py *.txt recursive-include doc *.html *.png *.txt *.css *.example recursive-include detectors *.py README.txt global-exclude *.pyc *.pyo .DS_Store *.orig *.rej *~ \#* include demo.py *.txt include doc/conf.py doc/roundup-favicon.ico exclude doc/security.txt include locale/*.po locale/*.mo locale/roundup.pot
