[Req]>>file size limit!!!

[JJoe]

(Sep. 12, 2013 04:28 PM)caspereg Wrote:  i tried to create a Range header
the problem is how to match the lower and the upper ranges
Range: bytes=low range-high range

That is not trivial but could be possible. Content-Range header provides info that might be used to create the next Range header. A blocklist could be used to create pseudo global variables.

My understanding of typical Range use: browser request is incomplete then next request browser may use Range to get more.

If I add

Code:

[HTTP headers]
In = FALSE
Out = TRUE
Key = "Range: test"
Replace = "bytes=0-500"

, the server returns

Quote:HTTP/1.1 206 Partial Content
Content-Type: image/jpeg
Content-Length: 501
Connection: keep-alive
Server: nginx
Date: Fri, 05 Apr 2013 00:49:42 GMT
Cache-Control: no-store, no-cache, max-age=0
Accept-Ranges: bytes
ETag: "2305750091"
Last-Modified: Wed, 06 Feb 2013 12:32:12 GMT
Content-Range: bytes 0-500/5736
Pragma: no-cache

as expected but the browser does not request the rest. You would need the browser to ask for more.
Assuming that the browser can be made to ask for more, would it know what to do with the pieces?