-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
InvalidArgumentBucket POST must contain a field named 'key'. If it is specified, please check the order of the fields.keyB #1
Comments
Have you modified any code specifically ? Sent from my iPhone
|
only think i modified was 'https://mybucket-dev123.s3-us-west-2.amazonaws.com/', |
and obviously the config.js: |
amazon wouldn't let me use the already existing mybucket-dev url so I had to append 123 to it. I also just changed aws.js |
Two things are possibly wrong here-
adding bucket to aws.js won't matter, since code doesn't use it. Let me know if the above helps otherwise we can debug more, next step would be to have a look at the exact 'POST' you are making. If the doesn't fix the problem, then paste your 'POST' here and/or you can email me the code changes you made and I can debug it to figure out what is wrong. I have added an issue to allow better integration of bucket name. |
Hm. No, neither of those seem to be it. I git add . and git commit the code with my changes but how to I push it on here so u can look? |
Use the fork and pull model https://help.github.com/articles/using-pull-requests Fork my repo On Tuesday, March 25, 2014, Matt Cowski notifications@github.com wrote:
Nukul Bhasin |
ah, beat ya to it :P MattCowski/s3-angular-file-upload@29b6be1 |
I will have a look first thing tomorrow Sent from my iPhone
|
Yea, i mean I barely changed anything. it's litterally just renaming the bucket to mybucket-dev123 so I think it's gotta be the stackoverflow issue above or something else. Thanks |
Instead of using - |
yes On Wed, Mar 26, 2014 at 4:58 AM, Nukul Bhasin notifications@github.comwrote:
|
I actually tried out your bucket and just uploaded a couple of pictures there. |
well actually, it was mybucket-dev123.s3.amazonaws.com ... is that On Wed, Mar 26, 2014 at 5:05 AM, Matt Cowski matt.cowski@gmail.com wrote:
|
no, that was a typo by me. I fixed it. |
checkout your bucket here - you will notice a couple of pictures uploaded to your bucket. |
WOW haha, you can access my bucket? how? without my keys / private key? |
When configuring the bucket we gave everyone permission if you followed the README |
Ah, makes sense. So what else can it be? |
what browser are you using? On Wed, Mar 26, 2014 at 6:12 AM, Matt Cowski notifications@github.comwrote:
Nukul Bhasin |
latest chrome Version 33.0.1750.152 |
Can you go to your 'chrome dev tools' and grab the exact POST you are On Wed, Mar 26, 2014 at 6:42 AM, Matt Cowski notifications@github.comwrote:
Nukul Bhasin |
dont really know if this is the right place
|
In chrome On Wed, Mar 26, 2014 at 6:51 AM, Matt Cowski notifications@github.comwrote:
Nukul Bhasin |
|
so under Network, I see |
Oh, I think you meant this: |
There is one evident difference between your request and mine and that order in which the file appears in the request payload. Yours is at the top whereas for me its at the bottom. I suspect that is why we are seeing the error. Yours
Mine
|
@danialfarid thoughts? The problem here seems to be that for some unknown reason when @MattCowski uploads to s3 the form-data; name="file" ends up at the bottom of the request for me whereas for @MattCowski its at the top of his request before form-data; name="key" |
What version of angular-file-upload are you guys using? It might be because of changes to new version 1.2.10 |
I am using ~1.2.9 What exactly could affect the order of form-data? I try an older version if you know one that would help debug. |
I released 1.2.11 which would add the data to the form-data first and then the file. @MattCowski could you confirm your version of angular-file-upload and try out the new version 1.2.11. |
I upgraded the version in this repo as well. |
The very latest v1.3.2
|
Sorry. Above is my version of fullstack.
|
Yea, I was on ~1.2.9. I upgraded but now I'm seeing "AccessDeniedAccess Denied"... |
Fixed! I changed my user policy and now it works! Thanks guys |
Hey, this demo is super helpful since I've also been using the yo fullstack, but I keep running into this:
InvalidArgumentBucket POST must contain a field named 'key'. If it is specified, please check the order of the fields.keyB
any clue how to fix?
The text was updated successfully, but these errors were encountered: