Previously this test sent:

at time = 0
```
> PUT /foo?expires=5 HTTP/1.1
> Expect: 100-continue
>
< HTTP/1.1 100 Continue
< HTTP/1.1 201 Created
```

at time = 10
```
> PUT /foo?expires=5 HTTP/1.1
> Expect: 100-continue
>
< HTTP/1.1 401 Unauthorizated
```

Since we do not receive 100-Continue, Java throws a ProtocolException instead of letting jclouds propagate its AuthorizationException in response to the 401.  Stripping 100 here allows jclouds to see the real 401 error.  I do not know if we should prefer this approach; 100-continue handling seems fragile between different services.

@diwakergupta relevant to your 100-continue investigation.