I apologize for replying to myself, but... I'd like to ask again: What's up with the collapsed forwarding feature in Squid 3.x?
Henrik? Anyone? ;-) The only thing I could find is this tidbit: "Merging of collapsed forwarding postponed until further notice due to discovered problems with the patch. " -- Henrik Nordstrom (09 Jul 2003) I don't mean to be a pest, really, I am just very interested in the development of Squid 3.x and this is is a pretty major feature for reverse proxies. I am very willing to test and contribute bug reports, etc. Thanks, Jake On Mon, 27 Sep 2004 10:30:02 -0700 Jake Gold <[EMAIL PROTECTED]> wrote: > I am testing Squid 3.x (ESI, epoll, etc). Is there currently any solution or work > around to this problem for 3.x? Can I make Squid do anything to lessen load on the > backend servers when this happens? > > I couldn't find any recent information regarding the development status of this > patch except that it's not available for 3.x yet. Can you offer me any insight into > where this patch really is in the development process? Is it in active development, > etc? > > > Thanks! > Jake > > On Mon, 27 Sep 2004 18:38:35 +0200 (CEST) > Henrik Nordstrom <[EMAIL PROTECTED]> wrote: > > > > The latter. All requests for an expired object becomes misses until the > > new status of the object is known. > > > > There is a existing project to optimize this considerably: > > > > http://devel.squid-cache.org/projects.html#collapsed_forwarding > > > > Regards > > Henrik > >
