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

New HTTP Client Processor Field for Ignoring Timeout Error #81

Open
gramian opened this issue Aug 22, 2024 · 0 comments
Open

New HTTP Client Processor Field for Ignoring Timeout Error #81

gramian opened this issue Aug 22, 2024 · 0 comments
Labels
enhancement New feature or request needs investigation It looks as though have all the information needed but investigation is required

Comments

@gramian
Copy link
Contributor

gramian commented Aug 22, 2024

Dear All,
I would like to propose a new configuration field for the http client processor, which allows to ignore exceeded timeouts. This boolean field could, for example, be named ignore_timeout and be by default false. This field may or may not regard retries, however, after the first or last time-out respectively, no connection error is fired, but instead an empty object {} is passed down-stream.

- http:
    url: "http://10.0.0.0"
    verb: "GET"
    ignore_timeout: true

This is useful for requests that are expected to time-out. For example if a request triggers a long running action (think hours) with variable runtime, of which its state can be checked through other means.

See: https://discord.com/channels/746368194196799589/754099840354615296/1276137809941495829

@mihaitodor mihaitodor added enhancement New feature or request needs investigation It looks as though have all the information needed but investigation is required labels Aug 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request needs investigation It looks as though have all the information needed but investigation is required
Projects
None yet
Development

No branches or pull requests

2 participants