fix(relayproxy): Remove Timeout middleware #2864
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The
Timeout
middleware is bringing more problems than it solves (see #2758), since as the maintainer ofecho
are saying this is better not to use it rather trying to solve all the issues it brings.I have decided to stop trying to manage a server timeout, this gonna be the client responsibility to handle it (and we will handle it in the different OpenFeature providers).
Note
This breaking change is minimal, if you continue to use the property
restApiTimeout
in your configuration file, it will be ignored.Checklist
README.md
and/website/docs
)