Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Set 304 status on ServerResponse when ETag/LastModified match [SPR-16348] #20895
When Controller returns 200 OK and Mono<ResponseEntity<String>> with Etag HTTP header, second GET will result in 304 HTTP status, if client sends correct If-None-Match HTTP header.
Same behaviour would be expected with WebFlux.fn and ServerResponse and using 'Cache-Control', 'ETag', and/or 'If-Modified-Since' HTTP headers
Attached sample which reproduce the problem with two endponts: /contoller & /handler
Referenced from: commits c53c8bf