Etag handling in Attract shots #49555
Labels
No Label
legacy project
Infrastructure: Websites
legacy project
Pillar
legacy project
Pillar Framework
legacy project
Pillar Website
Priority::High
Priority::Low
Priority::Normal
Status::Archived
Status::Confirmed
Status::Resolved
Type::Bug
Type::Design
Type::Patch
Type::Report
Type::To Do
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: archive/pillar#49555
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We should consistently handle Etags in Attract. At the moment we have the following shot operations. Create operations are not listed, since there is no Etag handling needed then.
The question mostly is whether we'll do Etag checking at all for these operations.
Tasks are less interesting, since we can only edit them from the web, and with simple PUT requests. This means that we can keep the current Etag handling (PUT only allowed if your web form contains the current Etag).
Changed status to: 'Open'
Added subscribers: @dr.sybren, @fsiddi