hi. this might belong on squid-dev, but figure i'll try here first. squid doesn't know if an object is even cacheable until it gets the headers back from origin, thus collapsed forwarding seems to impair performance of non-cacheable content, by blocking what will have to be a separate request anyway. most site administrators know what's cacheable or not on their site, and could craft regex to differentiate thus collapsed_forwarding being acl-based would be extremely beneficial, but it appears to be global on/off today. is this conclusion correct? are there any architectural reasons why it would be a bad idea? another way to optimize it would be to restrict it to revalidations only, not misses. then it would only apply to what is known to have been cachable. -neil
