Hi all,
I have been trying to use the Official AWS C# client library to interact with a local Walrus service (running Ubuntu Enterprise Cloud 10.04) . Initially I was having trouble with Authentication due to the difference in the service path between S3 and Walrus. Now I get a seemingly valid response to a GET on the service, with the following body
< ListAllMyBucketsResponse xmlns="http://s3.amazonaws.com/doc/2006-03-01/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" >
< ListAllMyBucketsResponse >
...
< /ListAllMyBucketsResponse >
< /ListAllMyBucketsResponse >
Any Idea why the < ListAllMyBucketsResponse > element is wrapped in another < ListAllMyBucketsResponse > element? Or why the < ? xml ... directive is missing? It seems like boto and other tools can make up for this poorly formatted xml. Unfortunately, C#'s Xserializer is a little more picky.
Any one else come across some good C# client libraries for communicating with Walrus?
Hi there,
It looks like the message has wrong name: it should be "ListAllMyBucketsResult", instead of "ListAllMyBucketsResponse", according to S3 API (http://docs.amazonwebservices.com/AmazonS3/2006-03-01/API/). If you somehow manually replace "ListAllMyBucketsResponse " with "ListAllMyBucketsResult", XML deserialization will succeed. Thank you for letting us to know this problem!
It turns out Eucalyptus correctly generate response following S3 WSDL definition (http://s3.amazonaws.com/doc/2006-03-01/AmazonS3.wsdl). However, the AWS .NET SDK expects the response format according to S3 API documentation. So, there's inconsistency between S3's WSDL definition and API documentation, and Eucalyptus follows WSDL in this case.
Can you please tell me how to connect to local walrus service using AWS c#. Because when i tried to connect it is always giving me bad request or Internal server error. I dont get a valid response at all. Please help me. You can check my post for a details,
http://open.eucalyptus.com/forum/walrus-access-through-c-error
Hi Reuben,
I ended up using the Affirma Three Sharp wrapper and modifying the connection. I.e. SSL off, different port, different base host name. This was a long time ago so I can't give much more details than that. I found that the AWS S3 libraries were not compatible without changing all of there xslts (which I didn't want to do).