From bfcf4ea81868e45477a680bd244cc0c38aac0ad5 Mon Sep 17 00:00:00 2001 From: Fabrice Bibonne Date: Mon, 21 Jul 2025 09:44:59 +0200 Subject: [PATCH] Document HTTP range request constraints See gh-35227 Signed-off-by: Fabrice Bibonne --- framework-docs/modules/ROOT/pages/web/webmvc/mvc-range.adoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/framework-docs/modules/ROOT/pages/web/webmvc/mvc-range.adoc b/framework-docs/modules/ROOT/pages/web/webmvc/mvc-range.adoc index f47c85cb79e..7e38dc4954e 100644 --- a/framework-docs/modules/ROOT/pages/web/webmvc/mvc-range.adoc +++ b/framework-docs/modules/ROOT/pages/web/webmvc/mvc-range.adoc @@ -15,6 +15,8 @@ xref:web/webmvc-functional.adoc#webmvc-fn-resources[serves a `Resource`]. `Range support is also transparently handled when serving xref:web/webmvc/mvc-config/static-resources.adoc[static resources]. +NOTE: To be handled transparently, the `Resource` object must not be a `InputStreamResource` and, in case of an annotated controller returning `ResponseEntity`, the status of the response must be 200. + The underlying support is in the `HttpRange` class, which exposes methods to parse `Range` headers and split a `Resource` into a `List` that in turn can be then written to the response via `ResourceRegionHttpMessageConverter`. \ No newline at end of file