Mercurial > pub > Impl
view lib/IMPL/Web/OutOfRangeException.pm @ 422:b0481c071bea ref20150831
IMPL::Config::Container tests, YAMLConfiguration now works and tested
author | cin |
---|---|
date | Sun, 20 Aug 2017 00:20:41 +0300 |
parents | c6e90e02dd17 |
children |
line wrap: on
line source
package IMPL::Web::OutOfRangeException; use strict; use IMPL::declare { base => { 'IMPL::Web::Exception' => '@_' }, }; sub CTOR { my ($this,$range) = @_; #TODO: validate args $this->headers({ content_range => { $range->{units} . ' */' . $range->{length} } }); } use IMPL::Resources::Strings { message => 'The specified range is invalid' }; sub status { "416 Requested Range Not Satisfiable" } 1; __END__ =pod =head1 NAME C<IMPL::Web::OutOfRangeException> A server SHOULD return a response with this status code if a request included a Range request-header field (section 14.35), and none of the range-specifier values in this field overlap the current extent of the selected resource, and the request did not include an If-Range request-header field. (For byte-ranges, this means that the first- byte-pos of all of the byte-range-spec values were greater than the current length of the selected resource.) =head1 DESCRIPTION When this status code is returned for a byte-range request, the response SHOULD include a Content-Range entity-header field specifying the current length of the selected resource (see section 14.16). This response MUST NOT use the multipart/byteranges content- type. =cut