http-client

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to realtime
2. Paste url wss://ris-live.ripe.net/v1/ws/?client=hoppscotch.io
3. Observe connect is disabled
4. Remove parameter, quickly undo it and click connect (also a bug)
5. Send { "type": "ris_subscribe" } to the remote server
6. Observe you receive

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.

Got has a very good coverage test-wise. Would be nice to port relevant tests that we're missing over to Ky.

Note: Not for https://github.com/sindresorhus/ky/blob/master/test/browser.js, but for everything else.

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

AnnotatedServiceBindingBuilder and VirtualHostAnnotatedServiceBindingBuilder currently don't share a common interface for its methods, such as pathPrefix() and exceptionHandlers(). This means, a contributor can add a builder method to one builder but not to the other by mistake. By making both builder extend a new interface AnnotatedServiceConfigSetters, we could prevent such a mistake.

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