> The HTTP client in
> this case is (always) a very particular embedded device with limited
> resources and a constrained operating environment.

Ok, so this is about working around a broken user-agent. I assume the vendor of that embedded device can't fix the crashing client?

How do you force the client to request the content in Byte-Ranges and not at once? Even if you are serving static files from the server (where nginx can provide most of the HTTP/1.1 features), the client actually needs to request it that way.


> It has yet to be seen whether this
> will solve the client crashing issues, so for now I'm going to leave
> it.

Meaning you still aren't sure whether range support will fix your client crashing issue? I would look for other workarounds, like heavy gzipping, (if x/html) minifying and outsourcing as much as possible in other files (css and stuff), etc. You already implemented checksumming on the client-side, maybe you can implement some segmenting in the application code as well, instead of relaying on HTTP to do that job via Range requests.


BR,

Lukas

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx