req
req copied to clipboard
Req is a batteries-included HTTP client for Elixir.
We're running into an issue with `into:` together with a `hostname` option, where when a HTTP2 connection is halted with `{:halt, {req, resp}}` response, something tries to close the HTTP2...
This issue is a starting point to discuss what the API for Telemetry events (emitted by Req) will look like. An initial sketch would be to have default events like...
In Mox, order matters: ```elixir Mix.install([:mox]) defmodule Foo do @callback upcase(String.t()) :: String.t() end Mox.defmock(Foo.Mock, for: Foo) ExUnit.start() defmodule Test do use ExUnit.Case import Mox setup :verify_on_exit! test "order matters"...
A lot of pages have this redirect flow: 1. user opens example.com/ 2. auth system adds cookie for user data, redirects again to example.com/ if cookie is not set 3....
Currently we can set `retry_log_level: :debug | :info | ... | false`. Besides log level it would be nice to format the log _message_ and I think we can achieve...
It’s a Finch adapter option but we can use it in test adapter too.
When upgrading Req (https://diff.hex.pm/diff/req/0.4.14..0.5.1), I noticed v0.5.0 changed how the authorization header is redacted, from `[redacted]` to `foo*****`, giving out both the first 3 characters and the length of the...
Currently when I make a request through Req, I have a setup where I parse the URL scheme in order to determine whether I need to apply a sha1withrsa override...
I'm thinking that it would be nice to have the ability to define your own `retry` function, and in the `retry` function if the conditions that I care about don't...