Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook



The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic

Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.

If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.

Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.

Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Amazon S3 request IDs

  • Filter
  • Time
  • Show
Clear All
new posts

  • Amazon S3 request IDs

    How can I retreive the Amazon request ID for the action of uploading a file to an Amazon s3 bucket?
    I have a button in a grid which does this action via action javascript and was wondering how to obtain the request ID.
    Is it via some of the logging files? Can I run some javascript action in this file upload action sequence?

  • #2
    Re: Amazon S3 request IDs

    I don't recognize the term "request ID" for Amazon S3. Where is it that you're seeing this?


    • #3
      Re: Amazon S3 request IDs

      Its an issue im having with uploading files to amazon s3 buckets. Amazon support have asked for the request id.
      The only error msg so far is 'xhr error'


      • #4
        Re: Amazon S3 request IDs

        Not sure if it's still like this, but I found (at one time) that not all S3 Buckets are the same. What Region is your Bucket in?
        And... do you have CORS set up? Are Permissions set up?


        • #5
          Re: Amazon S3 request IDs

          The buckets are all in the same region and are all connected with the same account, etc. The CORS configuration is identical for each bucket and permissions are also the same.
          I can upload files successfully to one bucket, but have XHR error when I attempt the exact same procedure with another bucket.
          I've tried all sorts of changes - renaming, permissions, etc but nothing seems to work. I've used amazon S3 for some time now and I now require another bucket for another client's application. I've purchased Amazon technical support plan in order to try and get this sorted and they have asked for a series of logs, debugging info, etc and in particular the Amazon request id.
          How can this be retrieved from the file upload action?


          • #6
            Re: Amazon S3 request IDs

            Ok... thanks... that 5th post should really have been your 1st. Context and information is nice to have.

            Run your Grid in Chrome and then right-click, Inspect, to open DevTools. There you should see a ribbon with buttons... Elements, Console, Sources, Network. Click the Network button. Run your Upload process... and then you'll see calls to S3. Click on a call and data for that call will display... Headers, Preview, Response, Timing. The Header tab will give you detailed information and includes the Request Id you may be looking for.


            • #7
              Re: Amazon S3 request IDs

              Thanks - that provided all the info needed!


              • #8
                Re: Amazon S3 request IDs

                Excellent... good to hear. So... what was the issue?


                • #9
                  Re: Amazon S3 request IDs

                  This issue is still not fully resolved, although I got the upload function working for the relevant S3 bucket. After resetting the CORS configuration a few times, etc it seemed to just work!
                  Perhaps when I require another bucket/application I'll make further progress with this.
                  Thanks again