conzorkingkong/cloud-storage

cloud-storage's Issues

Demo offline

Hey, I just wanted to let you know, that you're demo page is offline.

Example with caching

Can you give an example that uses caching?

I tried to do it by mimicking what is done here

but i cannot get a cf-cache-status: HIT

Here is my failed attempt:

addEventListener('fetch', event => {
  event.respondWith(handleRequest(event))
})


async function handleRequest(event) {
  if (event.request.method === 'GET') {
    let response = await serveAsset(event)
    if (response.status > 399) {
      response = new Response(response.statusText, { status: response.status })
    }
    return response
  } else {
    return new Response('Method not allowed', { status: 405 })
  }
}


async function serveAsset(event) {
  const url = new URL(event.request.url)
  
  const cache = caches.default
  let response = await cache.match(event.request)

  if (!response) {
    const { method, body } = event.request
    url.hostname = bucket + hostname
    response = await aws.fetch(url, { method, body })
    const headers = { 'cache-control': 'public, max-age=14400' }
    response = new Response(response.body, { ...response, headers })
    event.waitUntil(cache.put(event.request, response.clone()))
  }
  return response
}

Using with Digital Ocean Spaces get SignatureDoesNotMatch

I know you make this project to work with Amazon S3, but Digitan Ocean Space is compatible with V4Signer and, in theory, with S3 environment.

I builded your project and when I try to connect on Digital Ocean I get "SignatureDoesNotMatch" con cloudflare worker editor. I saw a lot of other projects (like s3cmd and softwares that use aws-sdk) getting the same error. I tested some solutions, but them not worked here. I think is not a V4Signer problem, maybe some header is wrong. I think I am not receiveing the true about what is happening on digital ocean spaces authentication.

I tried set appendSessionToken, allHeaders and singleEncode, but with no success. I get "Access denied" when signQuery is true.

I am using the right credentials and these attributions:

n = "jeanie",
r = ".nyc3.digitaloceanspaces.com",
a = new i.AwsClient({
            accessKeyId: "xxxxxxxxxxx",
            secretAccessKey: "xxxxxxxxxxxxx",
            region: "nyc3"          
        });

If I can guarantee:

• credentials are right
• v4 signatures are supported
• endpoint/url is right

What other problems can generate this error?