Section/Content To Improve
Section "Config order of precedence".

Suggested Improvement
The current implementation of

It's not clear from the website's documentation, or the --help output, how to do the following equivalent curl task:

Post a raw JSON query to ElasticSearch:

curl \
    --header "Content-Type: application/json" \
    --request POST \
    --data '{ "_source": [ "restricted_countries.*" ], "query": { "match_all": {} }, "size": 1000 }' \
    'http://localhost:9200/_search'

T

Description
Sending empty files in a multipart POST form is a proper use case due to web browsers supporting it.

I worked on a API layer using guzzle that had to work with an existing legacy codebase and trigger some actions (a proxy of some sort). There was a case where files had to be sent with empty content and would not work if you would omit them.

Example
_Currently no implem

Is your feature request related to a problem? Please describe.
An external API does not always respond successfully. Server errors for example 50x or 429 Too Many Requests may occur. Manually pressing the send button while waiting for a successful response can be tedious.

Describe the solution you'd like
Be able to set the number of retries and the expected/unexpected status codes o

If Vue.http.post gets called without passing in any data, the body of the request-body will contain a string "undefined".

This is a known quirk of IE11 (see MR on superagent)

Note: This only happens if Object.assign is being polyfilled - not if the internal assign-util is being called.

Long story short

Regression of #1188

Expected behaviour

Tests pass on armv7l

Actual behaviour

Test run fails at test_cookiejar.py:383: OverflowError

Steps to reproduce

Run tests

Your environment

linux 4.19
nixos 20.03
arm v7l
python 3.7
aiohttp client-3.6.2

Log

        ts_before = datetime.datetime(
            1975, 1, 1, tzinfo=datetim

Correct the terminology used in code and documentation so that it is consistent with HTTPie and web standards. Examples:

• body parameter -> data field
• operator -> separator

I think the docs are a bit thin. Would be nice with a tutorial on how to use the feature that takes advantage of all the options.

And sindresorhus/got#833 (comment)

Related to #781 and #517.

As described in #781, Feign overrides the timeouts configured in my Apache RequestConfig, even if I don't set custom request options in the Feign builder. This is unexpected behavior.

The change introduced to fix #517 copies the existing RequestConfig, but then immediately overwrites the timeouts, again, even if no Feign request options are set.

In the future, when Ky is more mature, we should add a comparison table to the readme. Like https://github.com/sindresorhus/got#comparison

There used to be only one type of operational error from node-fetch: FetchError.

This is no longer the case as I can count at least six: Error, NodeError, TypeError, SyntaxError, AbortError and FetchError. All of them can be triggered in one way or another through invalid response.

We would like to unify them in some ways but it's (a) a breaking change, (b) sometimes not standa

The documentation for Object, Var and Varholder lead me to believe that given the following setup:

std::vector<DynamicStruct> testList;
  Object t1;
  t1.set("name","com.tl");
  t1.set("num1",false);
  Object j;
  j.set("testval",testList);

The following call would let me extract the values (similar to my other use of Object with primitives and basic strings)

` auto retB

To Reproduce

From the documentation Adding Parameters (body() in the docs should be body):

	Fuel.post("https://httpbin.org/post", listOf("foo" to "foo", "bar" to "bar"))
		.also { println(it.url) }
		.also { println(String(it.body.toByteArray())) }

Expected output

https://httpbin.org/post
"

The fsockopen.after_request and curl.after_request hooks don't receive an $info parameter when a non-blocking request is sent.

This means the hook signature differs depending on whether the request is blocking or not, and conflicts with the hook docs.

Possible solution: Pass an empty array as the $info parameter for thes

A Spring Boot user has reported a problem with Spring Boot's reference documentation linking to Jetty's documentation. Spring Boot's reference documentation links to the Jetty documentation for the specific version of Jetty that it built against. For example, the documentation for Spring Boot 2.2.4 links to https://www.eclipse.org/jet

At present, reqwest only sends ALPN when rustls is used -- this effectively breaks http2_prior_knowledge when used with TLS, which is it's primary use case if the user does not use rustls.

Simply adding the rustls-tls feature to reqwest is insufficient to use rustls which can lead to confusion as the error message encountered when not using rustls is as follows:

reqwest::Err

HTTP.get(nil)
HTTP::Request::UnsupportedSchemeError (unknown scheme: )

HTTP.get('')
HTTP::Request::UnsupportedSchemeError (unknown scheme: )

HTTP.get('/')
HTTP::Request::UnsupportedSchemeError (unknown scheme: )

HTTP.get(':')
Addressable::URI::InvalidURIError (Cannot assemble URI string with ambiguous path: ':')

Ideally it should return InvalidURI exceptions if the URL is

https://www.boost.org/doc/libs/1_71_0/libs/beast/doc/html/beast/using_websocket/timeouts.html says

The timeout features of the TCP or basic stream should not be used when working with a websocket stream.

and

`The timeouts on the websocket stream are incompatible with the timeouts used in the tcp_stream. When constructing a websocket stream from a tcp stream that has timeouts enabled, th

In our codebase, we push RequestContext and immediately run some code with try-with-resources.
For example:

try (SafeCloseable ignored = ctx.push()) {
    logger.trace(decorate(msg));
}

If RequestContext provides run(Runnable) or call(Callable) we can reduce boilerplate code and simplify it.

ctx.run(() -> logger.trace(decorate(msg));

This is inspired by g

The documentation of the timeout module says:

If your goal is to cut off any request after a set amount of wall clock time, consider having a second “watcher” thread to cut off a slow request.

How would that work?

It seems like it is [strongly discouraged or even impossible](https://sta

Swagger supports adding examples along with spec: https://swagger.io/docs/specification/2-0/adding-examples/

We can add support to use swagger file as an input to vscode-restclient. This will save developers from maintaining 2 separate files for documenting REST APIs, swagger.yaml and restclient.http

Thank you for HTTP, and thank you for the recent additions of the logging and event logging system - they were very easy to use, and very helpful. 💯

https://github.com/http-kit/http-kit/blob/495219c40f86488351c6cc604df155a7a5b1a065/src/java/org/httpkit/server/RingHandler.java#L236-L238

I've been investigating a problem in my system where requests are being sent to a server that is being s

Affected file: grab/document.py

>>> import libgenapi
... /usr/local/lib/python3.9/site-packages/grab/document.py:35: DeprecationWarning: defusedxml.lxml is no longer supported and will be removed in a future release.
  import defusedxml.lxml

The defusedxml.lxml subpackage will be removed in a future release, so be