Archived Forum Post

Index of archived forum posts

Question:

Xojo Amazon S3 Listbuckets

Mar 15 '16 at 05:07

Hi,

I'm testing the S3 support in your Xojo plugin.

When running your example: S3 Listbuckets I end up getting two errors from time to time:

The first one is:

ChilkatLog:
  get_OAuthVerifier:
    ChilkatVersion: 9.5.0.56
  --get_OAuthVerifier
--ChilkatLog

And the second one is:

ChilkatLog:
  S3_ListBuckets:
    DllDate: Jan 30 2016
    ChilkatVersion: 9.5.0.56
    UnlockPrefix: Anything for 30-day trial
    Architecture: Little Endian; 32-bit
    Language: MAC OS X C/C++
    VerboseLogging: 0
    stringToSign: GET

Thu, 03 Mar 2016 09:27:26 +0000
/
    Authorization: AWS ”AKIAJDEHOBCROZWSXNUQ:WY2f741SGsuvow+ZyJ1Z7Q1w/Po=
    httpRequestStr:
      a_quickReq:
        quickHttpRequest:
          httpVerb: GET
          url: http://s3.amazonaws.com/
          openHttpConnection:
            Opening connection directly to HTTP server.
            httpHostname: s3.amazonaws.com
            httpPort: 80
            ssl: 0
            HTTP connection succeeded.
          --openHttpConnection
          buildQuickRequest:
            genStartLine:
              startLine: GET / HTTP/1.1
            --genStartLine
            addCookies:
              Not auto-adding cookies.
              sendCookies: 1
              cookieDir: 
            --addCookies
          --buildQuickRequest
          sendRequestHeader:
            sendHeaderElapsedMs: 0
          --sendRequestHeader
          statusCode: 403
          statusText: Forbidden
          readResponseBody:
            Response is chunked.
          --readResponseBody
        --quickHttpRequest
      --a_quickReq
      Returning failed status because of HTTP response code.
    --httpRequestStr
    Failed.
  --S3_ListBuckets
--ChilkatLog

I have verified that accesskey and secretkey are valid.

I can see the status code 403 in the last error but I'm not sure if there is anything I can do about that.

Best regards

Dan

---

Answer

Hi,

I'm feeling a bit embarrassed: I was testing with an slightly invalid AwsAccessKey.

Now it is working as expected.

I'm so sorry.

---

Answer

This should be fixed in the next version of Chilkat (to begin release in about 6 days). I will try to provide a pre-release ASAP so that you can verify.