> @@ -130,6 +131,10 @@ public void testSignPutUrlWithTime() throws Exception {
> String container = getContainerName();
> try {
> HttpRequest request = view.getSigner().signPutBlob(container, blob,
> 3 /* seconds */);
> + // Strip Expect: 100-continue since Java 7+ will throw a
> + // ProtocolException instead of setting the response code:
> + //
> http://www.docjar.com/html/api/sun/net/www/protocol/http/HttpURLConnection.java.html#1021
> + request = request.toBuilder().removeHeader(EXPECT).build();
@demobox this is an issue in any case where we send Expect: 100-continue but do
not receive HTTP/1.1 100 Continue, for example in this signed URL test, but
also in other scenarios such as Swift reauthentication #104 where we want to
consume the 401 response. Note that this is a Java 7 problem specifically, not
a jclouds problem, but we need to deal with it. @diwakergupta has discussed
offline stripping Expect: 100-continue by default and letting users opt into
this behavior if their service shows benefit from this, such as AWS-S3.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/183/files#r7008765
