I am building a Spring Reactive web application. Currently the logic is all working correctly but I noticed that everything is being run 3 times instead of 1.

I’m trying to determine if using @ControllerAdvice is appropriate to use to handle request that could have multiple http statuses (HTTP 207 Multi-Status). I have an existing API that includes several request that uses HTTP status 207. These particular request interact with an another application API so we capture that of those request and pass it along with the response status from our service. I’m wondering can @ControllerAdvice handle scenarios like this.

I’m trying to determine if using @ControllerAdvice is appropriate to use to handle request that could have multiple http statuses (HTTP 207 Multi-Status). I have an existing API that includes several request that uses HTTP status 207. These particular request interact with an another application API so we capture that of those request and pass it along with the response status from our service. I’m wondering can @ControllerAdvice handle scenarios like this.

I’m trying to determine if using @ControllerAdvice is appropriate to use to handle request that could have multiple http statuses (HTTP 207 Multi-Status). I have an existing API that includes several request that uses HTTP status 207. These particular request interact with an another application API so we capture that of those request and pass it along with the response status from our service. I’m wondering can @ControllerAdvice handle scenarios like this.

I’m trying to determine if using @ControllerAdvice is appropriate to use to handle request that could have multiple http statuses (HTTP 207 Multi-Status). I have an existing API that includes several request that uses HTTP status 207. These particular request interact with an another application API so we capture that of those request and pass it along with the response status from our service. I’m wondering can @ControllerAdvice handle scenarios like this.

I’m trying to determine if using @ControllerAdvice is appropriate to use to handle request that could have multiple http statuses (HTTP 207 Multi-Status). I have an existing API that includes several request that uses HTTP status 207. These particular request interact with an another application API so we capture that of those request and pass it along with the response status from our service. I’m wondering can @ControllerAdvice handle scenarios like this.

Description:
I am developing a Spring WebFlux application that integrates with a third-party API. This API returns data in the text/event-stream format, specifically for streaming chat messages. I have set up an endpoint in my application to forward requests to this API using WebClient and handle the SSE responses.

I have an internal framework using spring webflux for API development, which is working fine.

I have this RestTemplate which I want to migrate to WebFlux client:

I’m trying to convert a Spring Boot Web application to Webflux. Authentication is working for GET endpoints, but I can’t get past a 401 response on POST endpoints. I’m using the exact same postman calls that 1) worked before converting, and 2) works if I switch the POST to GET in the same request.