Set 304 status on ServerResponse when ETag/LastModified match [SPR-16348]

[spring-projects-issues]

Nikola Kolosnjaji opened SPR-16348 and commented

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.
This is not the case when using functional Endpoints.

Same behaviour would be expected with WebFlux.fn and ServerResponse and using 'Cache-Control', 'ETag', and/or 'If-Modified-Since' HTTP headers
reference: https://docs.spring.io/spring/docs/current/spring-framework-reference/web.html#mvc-caching-etag-lastmodified

Attached sample which reproduce the problem with two endponts: /contoller & /handler

---

Affects: 5.0.2

Attachments:

• etag.zip (52.80 kB)

Referenced from: commits c53c8bf

[spring-projects-issues]

Arjen Poutsma commented

Fixed in c53c8bf