-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
createPseudoDirectory always throws exception "A header you provided implies functionality that is not implemented" #295
Comments
These are the versions I encountered the issue with: Tested again today same computer, same install, but from a different network location and the issue disappeared. The first network location was an ADSL. And now I'm on cable broadband. Both are from same ISP. |
The SDK always sends a Content-Length header when sending requests to Amazon S3 (as that's required by S3). You can view what's being sent over the wire using verbose cURL output: http://docs.aws.amazon.com/aws-sdk-php/guide/latest/faq.html#how-can-i-see-what-data-is-sent-over-the-wire. Maybe that will show you something interesting (perhaps a redirect that is causing issues). |
I'm unable to reproduce this and it sounds like it works for you now based on your comment on May 26 . It's possible that you updated the SDK when testing on the new host, which is possibly the reason it works now. I'm going to resolve this issue, but feel free to reopen if you can provide verbose curl output for a failing case. |
Looks like a duplicate of aws/aws-sdk-js#15 but in php.
While using the stream-wrapper and creating a folder with mkdir, the createPseudoDirectory function is called and it passes an empty body to the putObject function. Which I suppose doesn't send a ContentLength header (didn't investigate).
Setting $params['Body'] to any value fixes this.
The text was updated successfully, but these errors were encountered: