On Wed, 2003-11-12 at 16:06, Carmona Perez, David wrote: > More info: > > > > With the caching pipeline, it always fails the first time and works ok > for sub-sequent times. > > Any idea of the cause?
Yes, it's because the content length is not set. When something is served from the cache, the size is known on beforehand so the content length can be set. To force the content length to be set, create a subclass of ResourceReader and override the shouldSetContentLength() method to return true. We should make this behaviour configurable though so that it's not necessary for everyone to create their own subclass. -- Bruno Dumon http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center [EMAIL PROTECTED] [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
