The default servlet knows how to handle ranges.
JSP's and servlets on their own do not understand ranges. (Because
typically custom code is written and out.println() is called).
The reason the default servlet can handle ranges is because the content
is static. The size of the resource is known so one can easily do range
checks appropriately.
JSP's/servlets content is generated on the fly. (Which is the main
reason you see chunked encoding since we don't know the content length
until your done serving the content)
That being said, you can make JSP's and servlets handle ranges by using
a Filter (which I don't of yet) which can buffer the content of the JSP
and only serve back the partial content as needed.
-Tim
James Abley wrote:
Hi,
I'm starting to see more clients making Range requests (iPhone among them)
and I'm trying to understand how much work I have to do to support the
correct behaviour. I've been investigating Tomcat support for this (although
my application will be deployed in different servlet containers; definitely
Tomcat 5.0.x, 5.5.x and Weblogic 9.x currently) and comparing my
expectations with what I'm seeing.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
