Closed james-hu closed 2 months ago
Hello, we will implement the new SDK Version, but the big problem is that it needs PHP Version >=5.5. I hope that the newer SDK Version will solve your Problem, but what schuld I do with users, that have the old PHP version.
Hi, Just tried the current version avialable as of this writing and it gave me this error still with the RM type Storage Account. Had to use Classic.
This might not work (i really don't know php), but for what to do with older PHP versions, why not check which version and only allow older SDK if older PHP ver and put text below account name indicating that php version is too low and can only use classic storage accounts?
Is classic still widely used anymore? Is everybody using new PHP now? Any plans for Resource Manager?
+1
+1
This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.
Background: in Azure there are currently two deployment model - Classic and Resource manager.
With 3.3 version, everything is fine if the Azure storage account is in "Classic" model. However, if it is of "Resource manager" model, this error message is shown:
Fail: Code: 400 Value: The value for one of the HTTP headers is not in the correct format. details (if any): <?xml version="1.0" encoding="utf-8"?>The value for one of the HTTP headers is not in the correct format. RequestId:89b387c1-0001-0020-2038-8ef721000000 Time:2016-04-04T06:10:24.9635417Z x-ms-version 2012-02-12 .
InvalidHeaderValue