http-client

Is there an existing issue for this?

• I have searched the existing issues

Summary

It would be amazing to have an Authorization tab on GraphQL, as it is for REST.

Why should this be worked on?

Authorization is also a thing in GQL and having automated OAuth mechanism would be 👍

Is your feature request related to a problem?

While setting the target interface's ip should work in most cases, it's possible that multiple devices have the same ip.

Also i'm having trouble using a wireguard vpn when i set Table=off. Table=off disables setting up the routes for the vpn and it justs shows up as a regular device. The connection is fine as pycurl can access it when i set

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.

node-fetch currently completely ignoring Content-Length header while consuming response.
Fetch specification about handling Content-Length on server response says almost nothing:
https://fetch.spec.whatwg.org/#concept-http-network-fetch (see whatwg/fetch#67)

On other hand, we have a fetch-node specific extension to limit the size of the response.

My prop

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

@trustin suggested an awesome idea to write a StreamMessage<T> into a File or Path. line/armeria#4044 (comment)

interface StreamMessage<T> {
    default CompletableFuture<Void> writeTo(Path destination, Function<? super T, ? extends HttpData> mapper, options...) {
        // Delegate to StreamMessages.writeTo(...)
    }
}

See httpie/httpie#1100 and httpie/httpie#1175