ShallowEtagHeaderFilter should make use of specified content length [SPR-8271] #12919
Labels
in: web
Issues in web modules (web, webmvc, webflux, websocket)
type: enhancement
A general enhancement
Milestone
Oliver Siegmar opened SPR-8271 and commented
The current ShallowEtagHeaderFilter implementation does not make any use of the content-length set by the content generating code. The attached patch re-initializes the ByteArrayOutputStream with the specified content-length. This improves performance on very busy sites with rather big files.
Affects: 3.0.5
Attachments:
Issue Links:
Referenced from: commits ae012ae
2 votes, 4 watchers
The text was updated successfully, but these errors were encountered: