http-client

Is your feature request related to a problem? Please describe.

I try to execute my first GET request and get this result:

I think the first-time-user experience could get improved here.

The hint to F12 vanishes soon, and I think accessing the error message via F12 is not a

Describe the bug

Originally, @asvetlov intended to delete any use of attrs from aiohttp 4.0+ series via aio-libs/aiohttp#5284. He dropped it from the runtime deps too.

But there are some places that still rely on attrs meaning that this will cause failures in runtime because of the missing dep. The tests currently succeed because attrs is listed as a test dep.

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')) {

For example, we do not provide these methods.

final GraphQLSchema schema = ...
sb.service("/graphql", GraphqlService.builder()
                                     .schema(schema)
                                     .runtimeWiring(c -> {
                                         final StaticDataFetcher bar = new StaticDataFetcher("bar");
                                         c.