Post Single Message - Incorrect location header

[Malini Kamalambal]

Summary : The location header returned is incorrect, when a single message is inserted (NOTE : The location header has the correct value, when more than one message is inserted)

Steps to Repro:
Post message to a queue, with a single message in the request body

Expected Result:
Location header will return the correct value

eg:
Location →/v1/queues/darngoodqueue/messages?51c9cd53821e7250f344eee1

Actual Result:

Location header is returned without 'messages' in the url.
i.e. Location → /v1/queues/darngoodqueue/51c9ce28821e7250f344eee2

[Kurt Griffiths (kgriffs)]

So, this is indeed an inconsistency that was done by design, but I would like to change it to always use the bulk schema. This report also uncovered a bug in the HTTP routes that I would like to fix:

/v1/queues/darngoodqueue?ids= 51c9cd53821e7250f344eee1

Should be, instead:

/v1/queues/darngoodqueue/messages?ids= 51c9cd53821e7250f344eee1

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/36319
Committed: http://github.com/stackforge/marconi/commit/4dfa19d403d506fe5a199577f582005419d1a5d9
Submitter: Jenkins
Branch: master

commit 4dfa19d403d506fe5a199577f582005419d1a5d9
Author: kgriffs <email address hidden>
Date: Thu Jun 27 10:54:31 2013 -0500

    Fix route for bulk-get message by ID

    This patch includes the following changes:

    * /v1/queues/my-queue?ids=1,2,3 => /v1/queues/my-queue/messages?id=1,2,3
    * Update Location header to suite
    * Always return the same schema for location header, regardless of the
      number of messages POSTed.

    Change-Id: I4559222e8f4685af1020c2743c26de699aef30dd
    Fixes: bug #1194571
    Fixes: bug #1165102