http-client

Describe the bug
Mostly when I navigate the text, I use CTRL + <- or CTRL + -> to navigate per word, but when I use it on the body editor it navigate through my browser history not per word.

To Reproduce
Steps to reproduce the behavior:

1. Open Hoppsctoot
2. Go to body
3. Change content type to application/json,
4. Write stuff,
5. Navigate using CTRL + Right or CTRL + Left

🐣 Is your feature request related to a problem? Please describe.
We had a report in aiohttp-session (see aio-libs/aiohttp-session#574) that a user submitting a 'large' cookie had the cookie dropped by the receiving browser.

According to RFC 6265 - section 6.1:

General-use user agents SHOULD
provide each of the following minimum

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

If a user performs a blocking task in decorator chains or services, they have to 1) submit a task to a blocking task executor,
2) pass the result to a CompletableFuture and 3) wrap the CompletableFuture with HttpResponse.from().

sb.serviceUnder("/web", service.decorate((delegate, ctx, req) -> {
    CompletableFuture<HttpResponse> future = new CompletableFuture<>();
    ctx.bl