It's the new 2.0.36 tag, up since Monday, 29-Apr-2002 18:12:28 PDT. Looks good so far.
This has a patch in server/core.c::sendfile_it_all which changes the existing AP_DEBUG_ASSERT to stat() the file before aborting. The existing assert trips if r->finfo.size is too big. The idea here is to see if the file size could be changing due to site updates in the middle of serving a file, or if it's clobbered memory or some such. My money is on the former. Let's say the file size is changing on us. What should we do about it? That means that the file we just served is probably garbage. The HTTP headers are long gone, so we can't do anything with them. Would it help to reset the TCP connection? Do we have an API? We could log an error, and return an error from sendfile_it_all. Greg
