Skip to content

ExchangeFilterFunction are applied in reverse order when chained with andThen #33700

@sruthigunti

Description

@sruthigunti

Configured ExchangeFilterFunction using andThen and expected them to be applied in the order provided. That is first handled for bad request, then retried and then handled for any other status codes. However any expection including 400 is handled by handleUnexpectedStatus() filter only.
WebClientExchangeFilter.zip

    @Bean
    public ExchangeFilterFunction webClientFilterChain() {
        return handleBadRequest()
                .andThen(retry())
                .andThen(handleUnexpectedStatus());
    }

Metadata

Metadata

Assignees

No one assigned

    Labels

    in: webIssues in web modules (web, webmvc, webflux, websocket)status: invalidAn issue that we don't feel is valid

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions