Roundup Tracker - Issues

Message7393

Author rouilj
Recipients marcus.priesch, rouilj
Date 2021-12-01.23:19:18
Message-id <1638400759.1.0.782605091101.issue2551175@roundup.psfhosted.org>
In-reply-to
Adding a little try/except/else block to the code above in the predicted spot
works. However the @etag value returned as part of the json payload doesn't have
the content-encoding suffix.

I claim this is not an issue as:

  the @etag value in the payload is not used by caches, proxies or other HTTP level
     transit nodes

  using the un-suffixed etag in an HTTP conditional header will (doesn't at the moment)
     still work and allow the change. This is fine as the use of etag in this case
     still works to prevent the lost update problem.

so I m not going to update the value of the payload's @etag value.
History
Date User Action Args
2021-12-01 23:19:19rouiljsetmessageid: <1638400759.1.0.782605091101.issue2551175@roundup.psfhosted.org>
2021-12-01 23:19:19rouiljsetrecipients: + rouilj, marcus.priesch
2021-12-01 23:19:19rouiljlinkissue2551175 messages
2021-12-01 23:19:18rouiljcreate