Browse Source

Document HTTP range request constraints

See gh-35227

Signed-off-by: Fabrice Bibonne <fabrice.bibonne@gmail.com>
pull/35329/head
Fabrice Bibonne 5 months ago committed by rstoyanchev
parent
commit
bfcf4ea818
  1. 2
      framework-docs/modules/ROOT/pages/web/webmvc/mvc-range.adoc

2
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 support is also transparently handled when serving
xref:web/webmvc/mvc-config/static-resources.adoc[static resources]. 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<Resource>`, the status of the response must be 200.
The underlying support is in the `HttpRange` class, which exposes methods to parse The underlying support is in the `HttpRange` class, which exposes methods to parse
`Range` headers and split a `Resource` into a `List<ResourceRegion>` that in turn can be `Range` headers and split a `Resource` into a `List<ResourceRegion>` that in turn can be
then written to the response via `ResourceRegionHttpMessageConverter`. then written to the response via `ResourceRegionHttpMessageConverter`.
Loading…
Cancel
Save