Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Override Client.read_timeout with Request #2512

Open
TAYTS opened this issue Dec 30, 2024 · 0 comments · May be fixed by #2531
Open

Override Client.read_timeout with Request #2512

TAYTS opened this issue Dec 30, 2024 · 0 comments · May be fixed by #2531

Comments

@TAYTS
Copy link

TAYTS commented Dec 30, 2024

Hi may I check if it is possible to add read_timeout option to Request to override the one in Client?

Wonder if it is not supported by design, didn't find relevant issues/discussions about it from the original feature issue(#2237).

The use case is there could be multiple upstreams and each may have different latency performance and given that we would want to create single Client and re-use instead of create multiple Client and each with different read_timeout config.

I am willing to work on it if this minor change is acceptable

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 a pull request may close this issue.

1 participant