Minor Description
In the new version of Wicket, AbstractResource parses the 'Range' header in the method 'setRequestRangeMetaData'. This method is always called.
Unfortunately, it is fundamentally broken. According to http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.35 a range request can contain multiple ranges. The current implementation only supports one range and throws a NumberFormatException when multiple ranges are requested.
Fortunately, a Resource supporting Range requests can override this method, but it also means that the CONTENT_RANGE_STARTBYTE and CONTENT_RANGE_ENDBYTE metadata are a flawed abstraction.