jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-656) Headers are not normalized when parsing Swift authentication response
Date Sat, 09 Aug 2014 00:36:12 GMT

    [ https://issues.apache.org/jira/browse/JCLOUDS-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14091505#comment-14091505

ASF subversion and git services commented on JCLOUDS-656:

Commit 99fe40ab91cf8edb5356beec1bcaf0a8ad602127 in jclouds's branch refs/heads/1.8.x from
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=99fe40a ]

JCLOUDS-656: Parse Swift authentication headers case-insensitively

Also ensure they are added to the result object with the normalized
capitalization expected by downstream code.

Follow-up to 375cb207.

> Headers are not normalized when parsing Swift authentication response
> ---------------------------------------------------------------------
>                 Key: JCLOUDS-656
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-656
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-blobstore
>    Affects Versions: 1.8.0
>            Reporter: Andrew Phillips
>            Assignee: Andrew Phillips
>              Labels: openstack-swift
>             Fix For: 1.8.1, 2.0.0
>         Attachments: JCLOUDS-656.patch
> When jclouds parses authentication response headers from Swift, it does not attempt to
recognize all of them case-insensitively. It also does not add them to the parsed object in
the normalized capitalization that is expected by downstream code.
> This is a more general case of JCLOUDS-155 that was not correctly fixed. See https://issues.apache.org/jira/browse/JCLOUDS-155?focusedCommentId=14087496&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14087496
> Reported by [~fabianlange]. Thanks, Fabian!

This message was sent by Atlassian JIRA

View raw message