Closed Bug 1242959 Opened 10 years ago Closed 9 years ago

v2 API should not support PUT

Categories

(developer.mozilla.org Graveyard :: BrowserCompat, defect)

Product:
developer.mozilla.org Graveyard
Component:
BrowserCompat
Platform:
All
Other
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: jwhitlock, Unassigned)

References

Details

(Whiteboard: [bc:infra][bc:milestone=spaceship])

What did you do? ================ 1. Log in as a user with edit privileges 2. Request OPTIONS /api/v2/browsers/6 with the application/vnd.api+json (JSON API v1.0) content type What happened? ============== PUT is in the Allow header, and metadata is included for a PUT action What should have happened? ========================== The list of allowed HTTP methods should be GET, PATCH, DELETE, HEAD, and OPTIONS. PUT is not an allowed HTTP method for JSON API v1.0 Is there anything else we should know? ====================================== Django REST Framework (DRF) prefers to use PUT for replacement of resources, so it may require replacing functionality (such as the UpdateModelMixin) used to implement the API. Some of this work might be done as part of bug 1230584.
Blocks: 996570
Mentor: jwhitlock
Whiteboard: [specification][type:bug] → [bc:infra][bc:milestone=spaceship]
Depends on: 1230584
Blocks: 1243225
No longer blocks: 996570
Mentor: jwhitlock
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
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.