Mercurial > p > roundup > code
view website/wiki/static/roundup/css/print.css @ 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 | 86c38b5aed66 |
| children |
line wrap: on
line source
/* print.css - MoinMoin Default Styles Copyright (c) 2001, 2002, 2003 by Juergen Hermann */ /* content styles */ html { font-family: Times, serif; font-size: 12pt; } body { /* Give about 3.4cm in Mozilla/Firefox and about 2.2cm in Safari */ margin: 1.5cm; } a, a:visited, a.nonexistent, a.badinterwiki { color: black; text-decoration: none; } a:hover { text-decoration: underline; } .info a { color: gray; } pre { font-size: 10pt; } a.interwiki:before, a.badinterwiki:before { content: attr(title) ":"; } a.interwiki img, a.badinterwiki img { display: none; } .footnotes div { width: 5em; border-top: 1pt solid gray; } /* user interface styles */ #header, #sidebar, #footer, #timings, #credits, #interwiki, #pagelocation { display: none; }
