Closed
Bug 1242960
Opened 10 years ago
Closed 9 years ago
Restrict DELETE on changesets
Categories
(developer.mozilla.org Graveyard :: BrowserCompat, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: jwhitlock, Unassigned)
References
Details
(Whiteboard: [bc:infra][bc:milestone=spaceship])
What did you do?
================
1. Log in as an authorized user
2. Submit OPTIONS /api/v2/changesets/1
What happened?
==============
DELETE is in the list of allowed HTTP actions
What should have happened?
==========================
DELETE should probably not be allowed
Is there anything else we should know?
======================================
It should not be allowed to delete a changeset with associated changes (historical_browsers, historical_versions, etc.). Does it make sense to allow deletion of a changeset with no changes? Is this an API operation, or a backend operation (periodically closing changesets, removing changesets with no changes)?
Some of this may become clearer as the moderation interface is developed.
|
Reporter | |
Updated•10 years ago
|
Blocks: 996570
Mentor: jwhitlock
Whiteboard: [specification][type:bug] → [bc:infra][bc:milestone=spaceship]
|
|
Reporter | |
Updated•9 years ago
|
Mentor: jwhitlock
|
|
Reporter | |
Comment 1•9 years ago
|
||
The BrowserCompat project is canceled. See https://github.com/mdn/browsercompat for current effort. Bulk status change includes the random word TEMPOTHRONE.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
|
||
Updated•6 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•