RangeItemHeaderValue Class

.NET Framework (current version)

The .NET API Reference documentation has a new home. Visit the .NET API Browser on docs.microsoft.com to see the new experience.

Represents a byte range in a Range header value.

Namespace:   System.Net.Http.Headers
Assembly:  System.Net.Http (in System.Net.Http.dll)


public class RangeItemHeaderValue : ICloneable

System_CAPS_pubmethodRangeItemHeaderValue(Nullable<Int64>, Nullable<Int64>)

Initializes a new instance of the RangeItemHeaderValue class.


Gets the position at which to start sending data.


Gets the position at which to stop sending data.


Determines whether the specified Object is equal to the current RangeItemHeaderValue object.(Overrides Object.Equals(Object).)


Allows an object to try to free resources and perform other cleanup operations before it is reclaimed by garbage collection.(Inherited from Object.)


Serves as a hash function for an RangeItemHeaderValue object.(Overrides Object.GetHashCode().)


Gets the Type of the current instance.(Inherited from Object.)


Creates a shallow copy of the current Object.(Inherited from Object.)


Returns a string that represents the current RangeItemHeaderValue object.(Overrides Object.ToString().)


Creates a new object that is a copy of the current RangeItemHeaderValue instance.

The RangeHeaderValue class provides support for a byte range in a Range header as defined in RFC 2616 by the IETF.

A Range header can specify multiple byte ranges.

An example of a byte-range in a Range header in an HTTP protocol request that requests the first 100 bytes would be would be the following:

Range: bytes=0-99\r\n\r\n

A HTTP server indicates support for Range headers with the Accept-Ranges header. An example of the Accept-Ranges header from a server that supports byte-ranges would be as follows:

Accept-Ranges: bytes\r\n\r\n

If an Accept-Ranges header is not received in the header of the response from the server, then the server does not support Range headers. An example of the Accept-Ranges header from a server that does not support ranges, but recognizes the Accept-Ranges header, would be as follows:

Accept-Ranges: none\r\n\r\n

Universal Windows Platform
Available since 8
.NET Framework
Available since 4.5
Portable Class Library
Supported in: portable .NET platforms
Windows Phone
Available since 8.1

Any public static ( Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.

Return to top