Mercurial > p > roundup > code
view website/issues/html/msg.index.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 | c2d0d3e9099d |
| children |
line wrap: on
line source
<tal:block metal:use-macro="templates/page/macros/icing"> <title metal:fill-slot="head_title" i18n:translate="" >List of messages - <span tal:replace="config/TRACKER_NAME" i18n:name="tracker"/></title> <span metal:fill-slot="body_title" tal:omit-tag="python:1" i18n:translate="">Message listing</span> <td class="content" metal:fill-slot="content"> <table tal:define="batch request/batch" class="messages"> <tr><th colspan=3 class="header" i18n:translate="">Messages</th></tr> <tal:block tal:repeat="msg batch"> <tr> <th><a tal:attributes="href string:msg${msg/id}"><tal:x replace="msg/id"/></a></th> <th tal:content="string:Author: ${msg/author}">author</th> <th tal:content="string:Date: ${msg/date}">date</th> </tr> <tr> <td colspan="3"><pre tal:content="msg/content">content</pre></td> </tr> </tal:block> <metal:block use-macro="templates/issue.index/macros/batch-footer" /> </table> </td> </tal:block>