On Nov 1, 2006, at 1:49 PM, Shane Cruz wrote:
The problem is that it's a pretty vague as a bug report.
If you had a HTTP trace that was clearly wrong, e.g. broken chunked encoding, then it would be a clear bug. Otherwise, it could be too many things to really narrow the problem down, e.g. JNI, flushing, buffering, char -> byte encoding, keepalive, or gzip or caching, etc. It would also depend on Resin standalone, Apache, or whatever. Those could be involved, too. So, yes, there have been fixes in all those areas since 3.1.14. :)
It probably wouldn't be the FileServlet itself, unless the browser is using the HTTP Range.
_______________________________________________ resin-interest mailing list email@example.com http://maillist.caucho.com/mailman/listinfo/resin-interest