Class ByteRangeRequest
Unsupported INTERNAL API! Not covered by semantic versioning; might change without notice. Helper class implementing RFC2616 14.35.1 Byte Ranges
Inheritance
Inherited Members
Namespace: EPiServer.Framework.Web.Internal
Assembly: EPiServer.Framework.AspNet.dll
Version: 11.20.7Syntax
public class ByteRangeRequest
Constructors
ByteRangeRequest()
Declaration
public ByteRangeRequest()
Properties
IsSingleRange
Declaration
public bool IsSingleRange { get; set; }
Property Value
Type | Description |
---|---|
System.Boolean |
Ranges
Declaration
public IList<ByteRange> Ranges { get; }
Property Value
Type | Description |
---|---|
System.Collections.Generic.IList<ByteRange> |
Methods
ProcessRangeRequest(HttpContextBase, Action<HttpContextBase, ByteRange>)
Unsupported INTERNAL API! Not covered by semantic versioning; might change without notice. Processes a range request
Declaration
public bool ProcessRangeRequest(HttpContextBase context, Action<HttpContextBase, ByteRange> transmitBitsFunction)
Parameters
Type | Name | Description |
---|---|---|
System.Web.HttpContextBase | context | The context |
System.Action<System.Web.HttpContextBase, ByteRange> | transmitBitsFunction | A method that can transmit the byte ranges |
Returns
Type | Description |
---|---|
System.Boolean | From RFC2616: If a syntactically valid byte-range-set includes at least one byte-range-spec whose first-byte-pos is less than the current length of the entity-body, or at least one suffix-byte-range-spec with a non-zero suffix-length, then the byte-range-set is satisfiable. Otherwise, the byte-range-set is unsatisfiable. If the byte-range-set is unsatisfiable, the server SHOULD return a response with a status of 416 (Requested range not satisfiable). Otherwise, the server SHOULD return a response with a status of 206 (Partial Content) containing the satisfiable ranges of the entity-body. |