ResourceRegionHttpMessageWriter should not use the response content-type [SPR-15358]

[spring-projects-issues]

Rossen Stoyanchev opened SPR-15358 and commented

When a request includes byte ranges, ResourceHttpMessageWriter delegates to ResourceRegionHttpMessageWriter. In that case the content type of the response has to be set to "multipart/byteranges" instead of to what it would have been if the full resource was written (e.g. "text/plain"). Each region is then written with the actual content-type in the boundary section.

ResourceRegionHttpMessageWriter extends EncoderHttpMessageWriter and has depended on the incorrect wrong behavior described under #19920. After the fix for #19920, each region is written with the content type of the response, i.e. "multipart/byteranges" instead of the actual content type, i.e. "text/plain".

---

Affects: 5.0 M5

Issue Links:

• Content-type resolution issue in EncoderHttpMessageWriter [SPR-15357] #19920 Content-type resolution issue in EncoderHttpMessageWriter

Referenced from: commits c735ffb