- From: Robert de Wilde <robert.de.wilde@online.nl>
- Date: Thu, 11 Jun 2009 12:14:20 +0200
- To: ietf-http-wg@w3.org
Sorry, the last part was cut off! The 'complete' HTTP header: HTTP/1.1 302 Found Content-type: multipart/parallel; boundary="ping" Content-length: 2048; Accept-Ranges: bytes; --ping Content-Id: Part1-ID Content-Range: bytes 0-511/2048 [..SomeContentWith512bytesOfLengh..] --ping Content-Id: Part2-Identifier Content-Range: bytes 512-1023/2048 Content-Location: http://sas4.domain.ext/resource/part2 --ping Content-Id: Part3-SomeRandom Content-Range: bytes 1024-1535/2048 Content-Location: http://sas2.domain.ext/resource/part3 --ping Content-Id: Part4-Reference Content-Range: bytes 1536-2047/2048 Content-Location: http://sas8.domain.ext/resource/part4 --ping-- Robert de Wilde wrote: > [..] > I order to try to find a way to catch one resource partially from > several locations I constructed this header: > http://pastebin.ca/1456435 > > [..] Lacking header [..] > > My question is if this Header would be accepted within the current > specification (from HTTP 1.1?)? If not, is there any thing I could > consider reconstructing to DO fit within the specs (and have the same > functionality)? > > [..]
Received on Thursday, 11 June 2009 10:14:55 UTC