Support missing properties from Content-Disposition spec [SPR-15555]

[spring-projects-issues]

Damiano Albani opened SPR-15555 and commented

The ContentDisposition implementation currently misses 3 properties which are described in the RFC2183 specification:

1. creation-date
2. modification-date
3. read-date

As in:

disposition-parm := filename-parm
                  / creation-date-parm
                  / modification-date-parm
                  / read-date-parm
                  / size-parm
                  / parameter

It would nice to have support for those parameters in Spring Web.

---

Affects: 5.0 RC1

Reference URL: #1443

Issue Links:

• Consider using ZonedDateTime in HttpHeaders [SPR-15661] #20220 Consider using ZonedDateTime in HttpHeaders

Referenced from: commits 97909f2

[spring-projects-issues]

Sébastien Deleuze commented

Juergen Hoeller As discussed with Rossen Stoyanchev, before merging this PR we should choose a strategy regarding to date/time that we previously exposed with long like in HttpHeaders.getAccessControlMaxAge().

• Should we continue to use long for consistency?
• Should we add Instant based variants and maybe deprecate long based ones?

Given the fact that date/time can be confusing for the users when not strongly typed and the Java 8+ focus of Spring Framework 5.0, I tend to vote for the latter.

Any thought? (this is a question we can also discuss during this afternoon meeting)

[spring-projects-issues]

Sébastien Deleuze commented

Fixed by using ZonedDateTime, I will create a follow-up issue targetted for RC3 in order to work on achieving consistency accross at least HttpHeaders API for the kind of property.