Project

General

Profile

Actions

Bug #6882

closed

POST create responses should be 201

Added by Daniel Lobato Garcia over 9 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
API
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

All api/v2 create responses are 200, with the except of interfaces.
However, the RFC specifies that when a resource is created, the server should return a 201 code, and a Location header with the location of the newly created resource.

process_success in base_controller needs to be changed to match the RFC.


Related issues 2 (1 open1 closed)

Related to Foreman - Bug #10356: POST and PUT should use RABL templates for the response.ClosedAlon Goldboim05/04/2015Actions
Copied to Foreman - Bug #11100: POST create responses should contain Location header of new resourceNew08/01/2014Actions
Actions #1

Updated by Alon Goldboim over 8 years ago

  • Related to Bug #10356: POST and PUT should use RABL templates for the response. added
Actions #2

Updated by Dominic Cleal over 8 years ago

  • Status changed from New to Closed
  • Assignee set to Alon Goldboim
  • % Done changed from 0 to 100
  • translation missing: en.field_release set to 63

Fixed via #10356.

Actions #3

Updated by Dominic Cleal over 8 years ago

  • Copied to Bug #11100: POST create responses should contain Location header of new resource added
Actions

Also available in: Atom PDF