On Fri, Apr 13, 2018 at 09:29:19PM -, john.calc...@gmail.com wrote:
> Just tried out s3proxy - it's exactly what we're looking for. I tried setting
> it up to use aws-v4 authorization against a filesystem backend like this:
>
> $ cat s3proxy.conf
> s3proxy.authorization=aws-v4
> s3proxy.endpo
> > I notice you filed a related bug against s3ninja recently -- you may
> > want to try S3Proxy[1] instead which has a more complete implementation
> > and actually uses jclouds as its backend.
Hi Andrew,
Just tried out s3proxy - it's exactly what we're looking for. I tried setting
it up to use
Thanks Andrew. Very helpful information. I'll definitely look at s3proxy.
John
On Fri, Apr 13, 2018, 12:06 AM Andrew Gaul wrote:
> On Thu, Apr 12, 2018 at 01:41:38PM -, john.calc...@gmail.com wrote:
> > Additional information on this issue: I've discovered by virtue of a
> wireshark session
On Thu, Apr 12, 2018 at 01:41:38PM -, john.calc...@gmail.com wrote:
> Additional information on this issue: I've discovered by virtue of a
> wireshark session that jclouds client is NOT sending chunked
> transfer-encoding, but rather aws-chunked content-encoding. Can anyone tell
> me why thi
Additional information on this issue: I've discovered by virtue of a wireshark
session that jclouds client is NOT sending chunked transfer-encoding, but
rather aws-chunked content-encoding. Can anyone tell me why this is necessary,
since A) it accomplishes the same thing that chunked transfer-en
On 2018/04/11 20:28:55, john.calc...@gmail.com wrote:
> I just found out that if I use "s3" provider type rather than "aws-s3"
> provider it works. I've set a breakpoint in the read(byte[], ...) method of
> my ByteBufferBackedInputStream and I can see that the difference appears to
> be that
I just found out that if I use "s3" provider type rather than "aws-s3" provider
it works. I've set a breakpoint in the read(byte[], ...) method of my
ByteBufferBackedInputStream and I can see that the difference appears to be
that the "s3" provider is using a straight upload, while the "aws-s3"
I've got a sample program here that shows uploading a payload via an
InputStream (ByteBufferBackedInputStream below - I've also tried it with a
FileInputStream). I can't use a ByteSource because it doesn't support sourcing
from direct access memory buffers.
```
public class App
{
public st
