Skip to content

Improve advice on response handling in an ExchangeFilterFunction #26819

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.

Sign up for GitHub

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

Jump to bottom
Closed
rstoyanchev opened this issue Apr 16, 2021 · 0 comments
Closed

Improve advice on response handling in an ExchangeFilterFunction #26819

rstoyanchev opened this issue Apr 16, 2021 · 0 comments
Assignees
@rstoyanchev
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: documentation A documentation task
Milestone
5.3.7

Comments

@rstoyanchev
Copy link
Contributor

We've deprecated the exchange() method on WebClient but if the response is handled at a lower level, in the ExchangeFilterFunction chain, it can lead to similar issues, for example reactor/reactor-netty#1603 (comment). This needs to be better emphasized in documentation..
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rstoyanchev rstoyanchev

Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: documentation A documentation task
Projects
None yet
Milestone
5.3.7
Development

No branches or pull requests
1 participant
@rstoyanchev