Mercurial > p > roundup > code
view website/www/Makefile @ 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 | 8e34362a14f7 |
| children | 977e0ef08406 |
line wrap: on
line source
TMP := _tmp HTML := html .PHONY: help clean html linkcheck help: @echo "Please use \`make <target>' where <target> is one of" @echo " html to make standalone HTML files" @echo " linkcheck to check all external links for integrity" clean: -rm -rf $(TMP) $(HTML) docs COPYING.txt docs: ln -s ../../doc ./docs ln -s ../../COPYING.txt html: docs mkdir -p $(TMP)/doctrees $(HTML) sphinx-build -b html -d $(TMP)/doctrees . $(HTML) linkcheck: mkdir -p $(TMP)/linkcheck $(TMP)/doctrees sphinx-build -b linkcheck -d $(TMP)/doctrees . $(TMP)/linkcheck @echo @echo "Link check complete; look for any errors in the above output " \ "or in .build/linkcheck/output.txt."
