Mercurial > p > roundup > code
view website/issues/html/_generic.404.html @ 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 | 8d595c5486c0 |
| children |
line wrap: on
line source
<!-- dollarId: issue.item,v 1.4 2001/08/03 01:19:43 richard Exp dollar--> <tal:block metal:use-macro="templates/page/macros/icing"> <title metal:fill-slot="head_title"> Item Not Found </title> <tal:block metal:fill-slot="body_title"> Item Not Found </tal:block> <td class="content" metal:fill-slot="content"> There is no <span tal:content="context/_classname" /> with id <span tal:content="context/id"/> </td> </tal:block>
