Mercurial > p > roundup > code
view website/www/contact.txt @ 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 | fefd8263ee4d |
| children | 6f5054751fb6 |
line wrap: on
line source
Contact ======= We maintain the following mailing lists: =================== ========================== roundup-users_ archives `[SourceForge]`__ roundup-devel_ archives `[SourceForge]`__ roundup-checkins_ archives `[SourceForge]`__ =================== ========================== These lists are moderated to protect them against spam. Please sign up if you intend to mail repeatedly. You may talk to Roundup developers directly via IRC irc://irc.oftc.net/roundup using IRC client or through WebChat_ interface. .. _roundup-users: https://sourceforge.net/projects/roundup/lists/roundup-users .. _roundup-devel: https://sourceforge.net/projects/roundup/lists/roundup-devel .. _roundup-checkins: https://sourceforge.net/projects/roundup/lists/roundup-checkins .. __: https://sourceforge.net/p/roundup/mailman/roundup-users/ .. __: https://sourceforge.net/p/roundup/mailman/roundup-devel/ .. __: https://sourceforge.net/p/roundup/mailman/roundup-checkins/ .. _WebChat: https://webchat.oftc.net/?randomnick=1&channels=roundup&prompt=1