Add mutate() to ClientResponse and deprecate from()
from() has the flaw of ignoring the body and it can't be fixed because
applications are guaranteed to be setting it already and if set twice
the builder drains the first body.
mutate() is a better fit in any case for what needs to be done in a
filter chain. It can be done more efficiently and is consistent with
similar options on the server side.
See gh-24680
@ -69,9 +69,9 @@ final class DefaultClientResponseBuilder implements ClientResponse.Builder {
@@ -69,9 +69,9 @@ final class DefaultClientResponseBuilder implements ClientResponse.Builder {
@ -81,21 +81,26 @@ final class DefaultClientResponseBuilder implements ClientResponse.Builder {
@@ -81,21 +81,26 @@ final class DefaultClientResponseBuilder implements ClientResponse.Builder {
@ -139,6 +144,12 @@ final class DefaultClientResponseBuilder implements ClientResponse.Builder {
@@ -139,6 +144,12 @@ final class DefaultClientResponseBuilder implements ClientResponse.Builder {
@ -151,11 +162,10 @@ final class DefaultClientResponseBuilder implements ClientResponse.Builder {
@@ -151,11 +162,10 @@ final class DefaultClientResponseBuilder implements ClientResponse.Builder {
@ -173,12 +183,12 @@ final class DefaultClientResponseBuilder implements ClientResponse.Builder {
@@ -173,12 +183,12 @@ final class DefaultClientResponseBuilder implements ClientResponse.Builder {