Closed
Description
Oliver Drotbohm opened SPR-14408 and commented
The HTTP 1.1 spec defines the Content-Disposition
header to contain a filename
attribute that servers can use to indicate the name of the file served. Currently, users of HttpHeaders
manually have to lookup the Content-Disposition
header and then parse the value to extract the filename.
It would be cool if the filename was either available directly or HttpHeaders
allowed to get access to a ContentDisposition
object, that provides access to the filename contained in it.
Affects: 4.3 GA
Issue Links:
- Reactive multipart request support [SPR-14546] #19114 Reactive multipart request support
- ResourceHttpMessageConverter should read the Content-Disposition header (if available) to get the file name [SPR-15191] #19757 ResourceHttpMessageConverter should read the Content-Disposition header (if available) to get the file name
- StandardMultipartHttpServletRequest cannot decode multipart Content-Disposition header encoded by FormHttpMessageConverter [SPR-15205] #19769 StandardMultipartHttpServletRequest cannot decode multipart Content-Disposition header encoded by FormHttpMessageConverter
- Overloaded convenience setters on HttpHeaders [SPR-16562] #21104 Overloaded convenience setters on HttpHeaders
Referenced from: commits 99a8510