Calling retry() on a Mono<> produced by calling WebClient.exchange() won't re-run the filters. This means any modifications made to the request by filters (like changing the URL for load-balancing purposes) won't be repeated.
DefaultWebClient seems to run all the filters synchronously, including generating the URL. Then DefaultExchangeFunction calls ClientHttpConnection. It's the http connection that does the actual connection asnychronously, producing a Mono<>. Specifically, filters get run when you call exchange() or retrieve(), not when you actually subscribe.
Related: spring-cloud/spring-cloud-commons#579
Calling
retry()on aMono<>produced by callingWebClient.exchange()won't re-run the filters. This means any modifications made to the request by filters (like changing the URL for load-balancing purposes) won't be repeated.DefaultWebClientseems to run all the filters synchronously, including generating the URL. ThenDefaultExchangeFunctioncallsClientHttpConnection. It's the http connection that does the actual connection asnychronously, producing aMono<>. Specifically, filters get run when you callexchange()orretrieve(), not when you actually subscribe.Related: spring-cloud/spring-cloud-commons#579