Describe the bug
Path: admin/malware_reports/<report_id>/
Currently, all warehouse admin pages reject duplicate POST keys via the reject_duplicate_post_keys_view, with one legacy exception.
When attempting to select and submit multiple releases to either quarantine or remove in the Detail View for a Malware Report, the submission will return an error:
400 Bad Request
The server could not comply with the request since it is either malformed or otherwise incorrect.
POST body may not contain duplicate keys (URL: '<host>/admin/malware_reports/<report-id>/quarantine_release/')
Expected behavior
On the malware report page, it should be possible to select multiple releases to be marked for quarantine or removal.
To Reproduce
- Login to an account that's marked as an observer
- Create a malware report for at project//submit-malware-report/
- From admin/malware_reports/ click through to the malware report page for the project
Issue 1: Failure to quarantine multiple releases:
- Click on Quarantine Release
- Select multiple releases
- Submit
- Results in a 400 error
Issue 2: Failure to remove multiple releases:
- Click on Remove Release
- Select multiple releases, enter a reason, confirm by typing the project name
- Submit
- Results in a 400 error
My Platform
Verified in a local development environment.
Additional context
Describe the bug
Path: admin/malware_reports/<report_id>/
Currently, all warehouse admin pages reject duplicate POST keys via the
reject_duplicate_post_keys_view, with one legacy exception.When attempting to select and submit multiple releases to either quarantine or remove in the Detail View for a Malware Report, the submission will return an error:
Expected behavior
On the malware report page, it should be possible to select multiple releases to be marked for quarantine or removal.
To Reproduce
Issue 1: Failure to quarantine multiple releases:
Issue 2: Failure to remove multiple releases:
My Platform
Verified in a local development environment.
Additional context