[
https://issues.apache.org/jira/browse/JCLOUDS-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14226385#comment-14226385
]
Fabian Lange commented on JCLOUDS-523:
--
Hi Adrian,
no the ticket is about
as requested. I did not include them before because the existing test was only
testing them, and also you mentioned in the issue that the fix is only
targeting the x-storage-url (which was not true because it tested all url
suffixes)
---
Reply to this email directly or view it on GitHub:
[
https://issues.apache.org/jira/browse/JCLOUDS-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14087496#comment-14087496
]
Fabian Lange commented on JCLOUDS-155:
--
Hi all,
it looks like the fix
[
https://issues.apache.org/jira/browse/JCLOUDS-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14087521#comment-14087521
]
Fabian Lange commented on JCLOUDS-155:
--
i patched this to put the expected case
[
https://issues.apache.org/jira/browse/JCLOUDS-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14087794#comment-14087794
]
Fabian Lange commented on JCLOUDS-155:
--
[~andrewp] yes i know that. and this patch
[
https://issues.apache.org/jira/browse/JCLOUDS-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14087796#comment-14087796
]
Fabian Lange commented on JCLOUDS-155:
--
The original patch did adress it correctly
[
https://issues.apache.org/jira/browse/JCLOUDS-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14087796#comment-14087796
]
Fabian Lange edited comment on JCLOUDS-155 at 8/6/14 3:46 PM
[
https://issues.apache.org/jira/browse/JCLOUDS-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14087812#comment-14087812
]
Fabian Lange commented on JCLOUDS-155:
--
sure,
HTTP headers are incorrectly treated
The problem reported in JCLOUDS-155 is that certain proxies lowercase
headers. This is especially a problem for the swift header
quot;X-Storage-Urlquot;, because it tells the client after authentication
where
to go to next.
The patch originally put the value into a CaseInsensitiveMap, but it was
Note that this is a patch for master, but the orginal issue is claimed to be
fixed in 1.6.2, 1.7.0. However that is not true. the bug was not fixed and
still existed in these versions.
Please backport the fix to all maintained branches.
---
Reply to this email directly or view it on GitHub:
[
https://issues.apache.org/jira/browse/JCLOUDS-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14087853#comment-14087853
]
Fabian Lange commented on JCLOUDS-155:
--
here is the PR:
https://github.com/jclouds
Fabian Lange created JCLOUDS-523:
Summary: Add support for Swift Api Auth
Key: JCLOUDS-523
URL: https://issues.apache.org/jira/browse/JCLOUDS-523
Project: jclouds
Issue Type: Bug
As a user of the current org.jclouds.openstack.swift.SwiftClient, I am heavily
confused by the change.
The labs.v1.SwiftApi is marked @Beta.
Deprecated means: You should not use it.
Beta means: You should not use it.
Deprecating a stable API without having a stable replacement is a no go for
I am not worried :) I am confused. In fact I plan to have a production version
of our software talking to os ceph via jclouds swift. But I don't know which
API to use. The deprecated one, or the beta one. I usually expect to find a
clear answer in code. and after beta and deprecation
Fabian Lange created JCLOUDS-522:
Summary: Swift API does not return null on getObject
Key: JCLOUDS-522
URL: https://issues.apache.org/jira/browse/JCLOUDS-522
Project: jclouds
Issue Type
[
https://issues.apache.org/jira/browse/JCLOUDS-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fabian Lange updated JCLOUDS-522:
-
Description:
similar to #JCLOUDS-521 getObject does not return null but also propagate the
404
16 matches
Mail list logo
