-
Notifications
You must be signed in to change notification settings - Fork 101
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
Chunked encoding upload is not supported on the HTTP/1.0 protocol (Again) #643
Comments
I have this problem too (with openstack.net v1.7.6) |
It still happen again. Don't have anyone can fix it ? |
This driver should probably be considered abandoned especially for anyone using with Rackspace. The previous maintainer worked for Rackspace which made sense as they had a vested interest for their cloud platform sdk. Rackspace have now communicated to clients that they're freezing product development and effectively end-of-life their cloud platform. This is causing us pain with regard to #650 |
@tommymonk |
At the moment this SDK is between maintainers, unless someone steps up it will remain in this state. We've contacted Rackspace to find if/when someone else from their dev team would take over from Carolyn (who no longer works for them) but were told it's unlikely due to the aforementioned road-map changes they're making following their acquisition by Apollo Global Management. Unlike yourself, we don't have the luxury of choosing a different openstack driver as the Rackspace driver depends on this one, and was also maintained by Carolyn. |
I have pulled the source code and updated the Flurl and Flurl.Http version. If anyone is still using this... |
is this resolved the issue? |
We appear to be experiencing the exact same effects as resolved by issue 333
A Windows service pushing objects into cloud files suddenly experiences many of the following exception and continues in this broken state until restarted
We're using openstack.net v1.7.7 and rackspace v0.2.0, the Windows service is running .NET 4.6.2 on Windows Server 2012 R2
The text was updated successfully, but these errors were encountered: