-
Notifications
You must be signed in to change notification settings - Fork 504
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
ListBuckets does not work on non-amazon services #171
Comments
I have the same problem, just with the deleteObject function, I also get the SignatureDoesNotMatch and I'm using DigitalOcean spaces |
@tpyo - Can you please take a look at this? |
Just odd that putObejct works fine, but not deleteObejct |
Hello guys, I'm facing the same issue, using Linode Object Storage |
I really hope it will be fixed, would hate begin using other overloaded classes just for that. |
Hello guys!
I'm kind of new to the amazon s3 service, and I'm making a few tests in order to integrate it to a Legacy PHP application, so this class is really useful for me, any help/improvements will be really appreciated, I can collaborate also :) |
Awesome @mblint-postcron, I'll test this in a bit (Using Digital Ocean spaces) and return back to you if it works for me too |
@mblint-postcron, where do you see this $s3->setSignatureVersion('v4') function? I can't find this function or one alike in the class? |
@mblint-postcron, hmm.. I don't get where you find this function. |
@mblint-postcron You there? |
Hi @Conver, sorry I was OOO. https://gist.github.com/mblint-postcron/d54f6785df3dbeeb955bdd3d901c7127 Let me know if it's working with the v2 |
Thanks @mblint-postcron, it works perfectly now with the v2 version! Thanks a lot. |
Here is an code example that I have here while trying to connect to Linode's S3 cloud storage service:
As a result, I get this error:
Warning: S3::listBuckets(): [403] Unexpected HTTP status in includes/S3.php on line 440
If I go into the file and print out the $rest object to get more information, I get:
On the other hand, if I change the above code to an amazon service:
Authentication works properly on Amazon's services.
Just to make sure this isn't a problem on Linode's end, I tried doing this on another third party (MojoCloud) and ran into the same issue.
Finally, just to make sure that the information is correct, I tried using aws-sdk-php beneath the tpyo library to see if I can connect to S3 using the same info:
And sure enough, this works for all three services (Amazon, MojoCloud, Linode). This way, I know the connection information is correct.
What I suspect here is a generalization problem with __getSignatureV4() where a valid signature is generated on amazon services, but not on non-amazon services.
Please let me know if any more information is needed here. If any of the maintainers here needs an access key / secret key to try troubleshooting this and debugging this on Linode's object service, please let me know.
Or if there's something obvious I'm missing, please let me know :)
The text was updated successfully, but these errors were encountered: