Secret creation fails without content-type specified

Bug #1321555 reported by John Vrbanac on 2014-05-21
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released
Steve Heyman

Bug Description

Request (Add X-Auth-Token header if you are testing against an endpoint with auth middleware enabled.):
curl -X POST -d '{
  "payload": "my-secret-here",
  "payload_content_type": "text/plain"
' http://localhost:9311/v1/12345/secrets

Status Code: 500
{"code": 500, "description": "Secret creation failure seen - please contact site administrator.", "title": "Internal Server Error"}

Expected Response:
Status Code: 201
{"secret_ref": "http://localhost:9311/v1/12345/secrets/a6a11dde-ad9b-48bb-85b8-a1774b5ddb8b"}

Steve Heyman (sheyman) on 2014-05-21
Changed in barbican:
assignee: nobody → Steve Heyman (sheyman)
description: updated
description: updated

Fix proposed to branch: master

Changed in barbican:
status: Confirmed → In Progress

Change abandoned by Steve Heyman (<email address hidden>) on branch: master
Reason: Rather than tolerate content type "errors" we will create a blueprint to propose enforcing content type correctness.

Changed in barbican:
status: In Progress → Fix Committed
importance: Undecided → Medium
milestone: juno-1 → juno-2
Changed in barbican:
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2014-10-16
Changed in barbican:
milestone: juno-2 → 2014.2
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers