Return-Path: X-Original-To: apmail-deltacloud-dev-archive@www.apache.org Delivered-To: apmail-deltacloud-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 11625DC81 for ; Tue, 4 Dec 2012 06:42:04 +0000 (UTC) Received: (qmail 42249 invoked by uid 500); 4 Dec 2012 06:42:02 -0000 Delivered-To: apmail-deltacloud-dev-archive@deltacloud.apache.org Received: (qmail 42129 invoked by uid 500); 4 Dec 2012 06:42:02 -0000 Mailing-List: contact dev-help@deltacloud.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@deltacloud.apache.org Delivered-To: mailing list dev@deltacloud.apache.org Received: (qmail 42030 invoked by uid 99); 4 Dec 2012 06:41:58 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Dec 2012 06:41:58 +0000 Date: Tue, 4 Dec 2012 06:41:58 +0000 (UTC) From: "jesus molina (JIRA)" To: dev@deltacloud.apache.org Message-ID: <1643763678.57736.1354603318549.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (DTACLOUD-386) CIMI frontend does not return Location in header when creating a Volume MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 jesus molina created DTACLOUD-386: ------------------------------------- Summary: CIMI frontend does not return Location in header when creating a Volume Key: DTACLOUD-386 URL: https://issues.apache.org/jira/browse/DTACLOUD-386 Project: DeltaCloud Issue Type: Bug Components: CIMI/Frontend Reporter: jesus molina According to CIMI specifications the HTTP header should return the Location of the created volume. The Location header is actually returned when creating a machine, but it is not when creating a volume, e.g. < Content-Type: application/xml < Location: http://localhost:3003/cimi/machines/inst53 < CIMI-Specification-Version: 1.0.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira