On Thursday, May 10, 2001, at 08:17 PM, Graham Leggett wrote:
Chuck Murcko wrote:
Can we review it for inclusion in mod_proxy++ (the HTTP/1.1 version) that we will package separately? Or should we wait and commit to -current after 1.3.20 is released?
[questions for the original poster]
The first two are a lot like the Header directive frommod_headers, inthat they allow you to set|unset|add|append to a given header. They also take an optional regular expression argument, which is matched against r->uri to control application of the directive.
Is there a reason why mod_headers can't be asked or modified to do this?
It might have something to do with the fact that the proxy is the only active 1.3 development going currently. Kwindla?
This is useful functionality I will agree, but I don't think adding more directives to do almost the same thing as we can already do is a good idea.
The last two are special-purpose directives that control the setting of Expires/Cache-Control and Date headers, respectively. They also take optional regular expressions to limit their application at request time.
ProxyResponseExpiresVector CacheFreshenDate
These two look like finer grained downstream cache control. Sites like Kwindla's with content obligations tend to need this sort of function a lot. Pretty much all the big sites I've seen implement this in some way, usually lots uglier than this. 8^)
This looks worthwhile to consider for the 2.0 cache, as well.
Chuck Murcko Topsail Group http://www.topsail.org/
