-
Notifications
You must be signed in to change notification settings - Fork 10
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
Uploading kernel to S3 fails (403 Forbidden) #8
Comments
I can certainly fix the error reporting a bit, but I haven't been able to reproduce a 403 forbidden message yet. I'll try with a different account on a different computer later today, though. |
For some reason the problem only happens on Chromium (I also tried Firefox and Midori). |
Hmmm, what version of Chromium? I have 28.0.1500.71 (209842) on OS X. Are you still on 28.0.1500.95, and what O/S? |
It was 29.0.1547.62 on Linux, but I just downgraded to 27.0.1453.110 and the same problem occurred. In the Network tab of the developer tools I see that the PUT to boot-xinu-os-org.s3.amazonaws.com failed with status 403. Perhaps it's a problem with how the (temporary?) access key is being sent? |
I think the 403 response from amazon s3 usually includes a xml document that says the forbidden reason, if it is the access key it should say something to that effect. You should be able to see it by double clicking the request and clicking the response tab. |
The response I got was:
|
Thanks. It looks like the mime type that chromium is sending to the s3 signer is incorrect (empty). I'm not sure why that is though. The Amazon response indicates that I signed with a "," as the mime type though, which is not what is in the corresponding request (which is just empty). I made a small change to force the mime type to be blank if it doesn't have a "/" in it, but I'm not sure if it'll work. If you get the chance can you try again and include the error response from amazon? (I have Fedora 19 with Chromium 27.0.1453.93, but it doesn't show the error. I'll try to find one of the versions you have though.) |
Still didn't work. Headers and response below.
|
Uploading a kernel fails (status 403 Forbidden) when sending it to S3.
Note that this error isn't reported to the user other than by turning the progress bar red, so I was initially confused about why it wasn't working.
The text was updated successfully, but these errors were encountered: