Commit Graph

4 Commits

Author SHA1 Message Date
Kevin van Zonneveld f67ce78c4d Bash script now correctly puts 2 parts.
So what triggered the previous error was an invalid range. What
remains weird is why a failed PUT would still be retrievable
2013-03-20 17:53:45 +01:00
Kevin van Zonneveld d4718fc6f0 Whitespace and small fixes 2013-03-20 17:53:09 +01:00
Kevin van Zonneveld e68f74faa0 put fails, but it looks like full data is still available.
The second PUT fails, the HEAD also claims to only have 3 bytes,
that would be inline with the fail. However the final get is able
to return the full 6 bytes. 3 of which are stored by the 2nd PUT that
was reported to fail.
2013-03-20 16:51:06 +01:00
Kevin van Zonneveld 6ac7656bec Demo script. Without a `tr -d '\r'`, this will currently hang the HEAD indefinitely 2013-03-20 16:19:31 +01:00