Skip to content

Conversation

@Onvember
Copy link
Contributor

No description provided.

and ``Keep-Alive:timeout=<keepalive_idle>``.
Otherwise Tarantool will send ``Connection:close``
* ``low_speed_time`` - set the "low speed time" -- the time that the
transfer speed should be below the "low speed limit" for the library
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Onvember @veod32 Just for testing gh comments

Setting this option to ``false`` allows to disable this behavior.
In this case, the HTTP client will return a 3xx response itself.
* ``accept_encoding`` - enables automatic decompression of HTTP responses
by setting the contents of the Accept-Encoding header sent in a HTTP
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

an HTTP

In this case, the HTTP client will return a 3xx response itself.
* ``accept_encoding`` - enables automatic decompression of HTTP responses
by setting the contents of the Accept-Encoding header sent in a HTTP
request and enabling decoding of a response when a Content-Encoding
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the Content-Encoding

by setting the contents of the Accept-Encoding header sent in a HTTP
request and enabling decoding of a response when a Content-Encoding
header is received. This option specifies what encoding to use.
It can be an empty string which means Accept-Encoding header will
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the Accept-Encoding

request and enabling decoding of a response when a Content-Encoding
header is received. This option specifies what encoding to use.
It can be an empty string which means Accept-Encoding header will
contain all built-in supported encodings. It also can be comma-separated
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

all supported built-in encodings

request and enabling decoding of a response when a Content-Encoding
header is received. This option specifies what encoding to use.
It can be an empty string which means Accept-Encoding header will
contain all built-in supported encodings. It also can be comma-separated
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

a comma-separated

header is received. This option specifies what encoding to use.
It can be an empty string which means Accept-Encoding header will
contain all built-in supported encodings. It also can be comma-separated
list of accepted encodings, like: ``"br, gzip, deflate"``. See also
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • supported encodings? is there any difference between accepted and supported encodings in this context?
  • also the question can be what the list is, what encodings are supported. So better to mention all of them here with minimal explanation. Info can be taken from the curl spec (your link below).
  • when you give a reference link like 'See also ...', it is better to mention why and for what info you are sending a reader there. Like "For details of the option, refer to..." or "Refer to curl specification for all the details on the option..."

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. I guess, no.
  2. gzip and deflate for usual build. br (brotli) can be enabled when building from sources against system curl.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants