> @@ -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();
Ah, OK. So the underlying problem is that we are setting Expect: 100 by default
in the first place (I recall the discussion) and, pending a solution for that,
the workaround _here_ is to prevent any problems from occurring.
For this test, though, aren't we able to predict the expected responses? I
mean, should we be getting a 401 here in the first place? Or is the fix simply
to make debugging easier so that if we _don't_ get a 100, we can more easily
see what _actually_ happened?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/183/files#r7009529
