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

Improve advice on response handling in an ExchangeFilterFunction #26819

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
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: documentation A documentation task
Milestone

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..

@rstoyanchev rstoyanchev added type: documentation A documentation task in: web Issues in web modules (web, webmvc, webflux, websocket) labels Apr 16, 2021
@rstoyanchev rstoyanchev added this to the 5.3.7 milestone Apr 16, 2021
@rstoyanchev rstoyanchev self-assigned this Apr 16, 2021
Zoran0104 pushed a commit to Zoran0104/spring-framework that referenced this issue Aug 20, 2021
lxbzmy pushed a commit to lxbzmy/spring-framework that referenced this issue Mar 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: documentation A documentation task
Projects
None yet
Development

No branches or pull requests

1 participant