Mercurial > p > roundup > code
view website/issues/html/home.html @ 5729:9ea2ce9d10cf
A few internet references report that etags for the same underlying
resource but with different representation (xml, json ...) should have
different etags.
That is currently not the case. Added code to allow incorporation of
representation info into the etag. By default the representation is
"json", but future patches can pass the representation down and modify
flow to match requested representation.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Sat, 25 May 2019 14:23:16 -0400 |
| parents | c2d0d3e9099d |
| children |
line wrap: on
line source
<!-- This is the default body that is displayed when people visit the tracker. The tag below lists the currently open issues. You may replace it with a greeting message, or a different list of issues or whatever. It's a good idea to have the issues on the front page though --> <span tal:replace="structure python:db.issue.renderWith('index', sort=[('-', 'activity')], filter=['status'], columns=['activity','title','creator'], filterspec={'status':['1','2','4']})" />
