Skip to content
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

S3 headObject Error: BadRequest: null #46

Open
aep opened this issue May 17, 2017 · 2 comments
Open

S3 headObject Error: BadRequest: null #46

aep opened this issue May 17, 2017 · 2 comments

Comments

@aep
Copy link

aep commented May 17, 2017

Message:
S3 headObject Error: BadRequest: null

Any idea how to get some useful error message?

@clineamb
Copy link
Owner

I believe that is from S3, so whatever they send through is what you're going to get unfortunately.

@clineamb clineamb reopened this May 24, 2017
@NZubia
Copy link

NZubia commented Mar 8, 2019

Hi!

I think this comments arrive to late but I had the same problem this days and I found how to solve it. I don't know if is the same but in my case I was using gulp-rev and its function rev.manifest, and my problem was that I was not sending the correct file (In my case was a javascript file) as in the following code:

gulp.src('javascriptFile.min.js') .pipe(rev()) .pipe(gulp.dest('./public/javascripts/resources/')) .pipe(rev.manifest(options)) .pipe(s3(params));

So as you can see I was uploading the manifest file instead of the javascript file. But when I change my code to this and I put the s3 pipe after my rev pipe all works!!

gulp.src('JAVASCRIPTSOURCE') .pipe(rev()) .pipe(s3(params));

I hope this can be helpfull for you

Regards

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants