Consider using ZonedDateTime in HttpHeaders [SPR-15661]

[spring-projects-issues]

Sébastien Deleuze opened SPR-15661 and commented

As raised during discussing #20114, ideally we Spring Framework 5 API should exposed date/time with timezone in a consistent way, but currently HttpHeaders existing date/time fields are exposed with long while they should be exposed with ZonedDateTime like ContentDisposition.

The consensus was to deprecate current long based variants and to add new ZonedDateTime ones, but this is not possible easily on getters if we use the same method name and choosing other names like getDateAsZonedDateTime() is not super appealing.

---

Affects: 5.0 RC2

Issue Links:

• Support missing properties from Content-Disposition spec [SPR-15555] #20114 Support missing properties from Content-Disposition spec
• MockHttpServletResponse.getDateHeader fails with NPE for non-existing header [SPR-16160] #20708 MockHttpServletResponse.getDateHeader fails with NPE for non-existing header
• Overloaded convenience setters on HttpHeaders [SPR-16562] #21104 Overloaded convenience setters on HttpHeaders
• Allow java.time types for setting the Last-Modified header [SPR-17571] #22103 Allow java.time types for setting the Last-Modified header
• Use fixed GMT time-zone for WebSessionManager Clock [SPR-15675] #20234 Use fixed GMT time-zone for WebSessionManager Clock

Referenced from: commits 1fa8410, 5c1d8c7

[spring-projects-issues]

Sébastien Deleuze commented

Merged, see the commit log message for more details.