Some XML documents have a flexible ordering that streaming XML parsers do not understand. This was recently seen when parsing S3 ListBuckets responses in apache/jclouds#103. Note that other documents, for example XHTML, have a meaningful order so this should not be a default option. @timuralp

In a specific test I want to enable the partial data failure for only S3 get object calls and not for any other RPC.

right now there's no way to deterministically induce chaos

it'd be good to have https support and induce chaos at the HTTPS layer

@timuralp suggests:

found an annoying bit about Swift's EC policy implementation: the object is reconstructed as part of streaming the response to client, so the client can get a 200 OK response and subsequently end up with a short read, because there is now way to indicate that a segment failed to be reconstructed

Provide a docker image to allow easy proxying.

Chaos HTTP Proxy supports writing partial data to the client then closing the socket. It should also support reading partial data from the client then closing the socket. Suggested by @zack-shoylev.