Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8543635
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 11, 20262026-06-11T12:21:09+00:00 2026-06-11T12:21:09+00:00

I am working with Amazon S3 on a HTML5 CORS file uploader. It’s working

  • 0

I am working with Amazon S3 on a HTML5 CORS file uploader. It’s working well, but I have still a very strange thing which is happening.

Before the PUT request to send the file, the browser always sends an OPTIONS request, which fails with a 403 FORBIDDEN error code.

But the file is correctly transferred to S3 so what’s happening ?

I tried to solve my problem by enabling all the HTTP methods, but it hasn’t worked.

Here are the headers I am using for the PUT request:

AWSAccessKeyId:XXXXXXXXXXXXXXXXXXXXXX
Expires:1347882643
Signature:YYYYYYYYYYYYYYYYYYYYY

And some code stuff :

var xhr = new XMLHttpRequest();
// bind the event listener
xhr.upload.addEventListener("progress", progress_listener, false);
// open the XMLHttpRequest 
xhr.open('PUT', signed_url, true);

// when the upload is completed call the callback function if supplied
xhr.onload = function(e) {
    if(typeof callback == "function") {
        callback(this.status == 200, file.name, file_id);
        confirm_upload_success(file_id);
    }
};

// start sending
xhr.send(file);
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-11T12:21:10+00:00Added an answer on June 11, 2026 at 12:21 pm

    EDIT: This bug has been fixed by Amazon 🙂

    Carl@AWS / Sep 28, 2012 2:56 PM:

    All,

    This bug should now be fixed and using pre-signed url’s with CORS will
    succeed.

    Thanks,


    The problem you describe is an Amazon bug: It turns out that S3 is currently authenticating the OPTION call that is made in “preflight” for CORS and that fails (probably because the auth has been signed with for a PUT request not an OPTION request).

    It’s already on their radar as you can see here: CORS works with public data, but fails to work with pre-signed request

    Carl@AWS / Sep 5, 2012 1:00 PM:

    Thank you, and everybody else, for the report. You are correct that
    pre-signed requests returning an error on the initial OPTIONS request.
    We are working on this issue and expect to add this support shortly. I
    don’t have a timeline for the availability of the change but I will
    update this thread with more information when I have that. If you have
    any follow up questions let me know.

    So just ignore it and they’ll fix it.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'm uploading to Amazon S3 using the iOS SDK which is working great but
I am working with amazon boto and I have 2 lists. List 1 contains
I am working on an interface with the amazon product advertising API. I have
I am working on a grails application which uses Amazon's SimpleDB. I changed a
I am working on an application that uploads a file to amazon s3(part of
Does anyone have any tips on working with Amazon S3 service and Flash? I
I'm trying to upload a file to Amazon S3 using Zend. Everything is working
I am working on integrating Amazon FPS into my company's website but seem to
I'm working on implementing an Amazon S3 uploader for my rails project. I'm trying
I am working with Amazon In-app-purchases for Android on flash using native extentions. So,

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.