Support multiple content-types

Bug #1507925 reported by Alvaro Lopez
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released

Bug Description

The HTTP specification states that multiple headers with the same field-name can be separated by commas [1]. rOCCI passes multiple content types under one field name. We should handle this.

[1] http://greenbytes.de/tech/webdav/rfc2616.html#message.headers

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to ooi (master)

Reviewed: https://review.openstack.org/237457
Committed: https://git.openstack.org/cgit/openstack/ooi/commit/?id=64688e792a2ad2c71cc213607b77c5934087ac4c
Submitter: Jenkins
Branch: master

commit 64688e792a2ad2c71cc213607b77c5934087ac4c
Author: Alvaro Lopez Garcia <email address hidden>
Date: Tue Oct 20 10:18:06 2015 +0200

    Handle multiple content-types into one header field

    HTTP specification states that multiple values for one header can be
    passed if separated by commas. rOCCI uses that for the content type,
    therefore we must support it.

    Change-Id: Ib02e6659e112ee9fb90da986339f2f749f0dbc87
    Closes-Bug: 1507925

Changed in ooi:
status: New → Fix Committed
Alvaro Lopez (aloga)
Changed in ooi:
milestone: none → 0.1
Alvaro Lopez (aloga)
Changed in ooi:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers