Returning non-standard HTTP status code causes exceptions on WebFlux [SPR-16073]

[spring-projects-issues]

Anders Aagaard opened SPR-16073 and commented

See https://gist.github.com/andaag/f30aeff3bda499bb159f50649a0eb353

When returning a Mono<ResponseEntity>, and the returned ResponseEntity has a custom http code, spring throws an java.lang.IllegalArgumentException: No matching constant for [555]

---

Affects: 5.0 GA

Issue Links:

• RestTemplate doesn't consistently tolerate unknown HTTP status codes [SPR-15978] #20529 RestTemplate doesn't consistently tolerate unknown HTTP status codes
• ResponseEntity should allow the usage of unassigned HTTP status codes [SPR-14205] #18779 ResponseEntity should allow the usage of unassigned HTTP status codes
• ServerResponse should allow the usage of unassigned HTTP status codes [SPR-16366] #20913 ServerResponse should allow the usage of unassigned HTTP status codes
• No support for non-standard HTTP status codes in reactive ClientHttpResponse [SPR-16748] #21289 No support for non-standard HTTP status codes in reactive ClientHttpResponse

Referenced from: commits 3890d4c

[spring-projects-issues]

Juergen Hoeller commented

We've addressed this for Spring MVC and RestTemplate already, so good catch, we need to address this for WebFlux as well.

[spring-projects-issues]

Juergen Hoeller commented

AbstractServerHttpResponse can store an HTTP status code as an integer value now, and ResponseEntityResultHandler passes it on as such.

[spring-projects-issues]

Anders Aagaard commented

Perfect, thank you very much.

(This is my first bug reported for spring... From initial report to fixed in about 3 hours. I'm pretty happy :p )