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

createPseudoDirectory always throws exception "A header you provided implies functionality that is not implemented" #295

Closed
xaben opened this issue May 25, 2014 · 4 comments

Comments

@xaben
Copy link

xaben commented May 25, 2014

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.

@miklos-martin
Copy link
Contributor

@xaben what version of the SDK and guzzle are you using? Can it be some region specific issue? In what region is your bucket?
I reported the same here: #273 but after a while the error was gone and I couldn't reproduce it anymore.

@xaben
Copy link
Author

xaben commented May 27, 2014

These are the versions I encountered the issue with:
aws/aws-sdk-php (2.6.5)
guzzle/guzzle (v3.9.1)
Bucket is in Ireland

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.

@mtdowling
Copy link
Member

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).

@mtdowling
Copy link
Member

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.

@diehlaws diehlaws removed response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. labels Apr 25, 2019
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

5 participants