I see the header malformed in the Rackspace console. If I debug code the blob seems to always have the header non-malformed but when putting in the cdn it gets malformed.

When blob is read back it contains the malformed header.

Hm...if it looks like it's being sent correctly *from* jclouds and ends up in Rackspace with invalid characters, perhaps it's something on the Rackspace side?

I hope one of the Rackspace experts on this list has more information...

ap

Reply via email to