http-client

Is your feature request related to a problem? Please describe.
Mostly maintainability and code readability. When you make a change to any of these renderers you are forced to copy the same code more than three times

Describe the solution you'd like
A global component for rendering the response that receives as inputs:

• The response
• List of actions and a callback for each of the

🐞 Describe the bug

TraceConfig.on_response_chunk_received doesn't trace if the response body is read from ClientResponse.content

This behavior isn't obvious when looking at Tracing Reference, [Streaming Response Content](https://docs.aiohttp.org/e

Hi, I have discovered issue when using feign.httpclient.ApacheHttpClient.
In some cases Apache client throws ProtocolException which is a checked exception. This happens for example when server returned 303 HTTP code but there was no location header.
In such case Feign proxy throws UndeclaredThrowableException instead of invoking ErrorDecoder.

From time to time i see ppl using data instead of body which is wrong.
happened just recently in node-fetch/node-fetch#481 (comment)

how do you feel about adding a little warning message that can only appear once. (kinda like node reports that you are using experimental apis)

if ('data' in bodyInit && notWarned) {
  console.warn('use body i

For some reason Amazon REST api's require the content-type to be set to "application/x-amz-json-1.1" instead of the standard "application/json"

Currently the content-type header is set automatically for json data overriding any headers passed in to the request.

It would be useful to first check if the header is set before overriding it:

if (!this.request.headers.set('content-type')) {

Just a suggestion.

I feel like Armeria's CookieBuilder makes it too easy to create an insecure service. Default of secure, http only, same site cookies and requiring a user to explicitly opt out would help prevent accidental cookie leaks without a real UX penalty when the use case does need something more lax.