Mercurial > p > roundup > code
view website/issues/html/home.about.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 | 4155ed7f00f4 |
| children |
line wrap: on
line source
<!-- dollarId: issue.index,v 1.2 2001/07/29 04:07:37 richard Exp dollar--> <tal:block metal:use-macro="templates/page/macros/icing"> <title metal:fill-slot="head_title" i18n:translate="" > About this Tracker </title> <tal:block metal:fill-slot="body_title" i18n:translate=""> About this Tracker </tal:block> <div class="content" metal:fill-slot="content"> <span tal:condition="not:python:request.user.hasRole('Admin')" tal:omit-tag="python:1" i18n:translate=""> Please login with your username and password to find out about this tracker. </span> <div tal:condition="python:request.user.hasRole('Admin')" tal:omit-tag="python:1" i18n:translate=""> <div tal:replace="structure python:utils.AboutPage(db)"></div> </div> </div> </tal:block>