Re: mod_proxy patches for HTTP Header manipulation

Graham Leggett writes:
...
>
> The basic problem is that by adding the code to the proxy, only the
...
>
> In theory mod_headers in v2.0 should be a filter, not a fixup. This way

Absolutely. I'll write to Paul Sutton, whose name is on mod_headers, and see if I can contribute to a v2.0 mod_headers rewrite.

...
>
> This is because when a cached file expires, the new revalidated cached

That's right. In fact, the first bit of hacking I did on the mod_proxy code was a simple "mark as being fetched" plus "just wait around for a bit if you find a stale-but-marked file" pair of patches to proxy_cache.c

But I decided to abandon that approach for a few reasons, the two most important being:

First, in the context of the 1.3.x development cycle, this seemed like a pretty big change in how the cache works. I thought it would be more likely that people would be receptive of a patch that doesn't do anything except operate on headers.

Second, though changing the cache to prevent lots of requests during the re-generate window did solve our traffic pile-up problem, it didn't address our need to decouple internal and external caching behavior for logging/etc reasons.

Do you need help?

In addition to our free technical library, Pantek provides professional IT services to companies who utilize Open Source software: Learn more about Pantek's Technical Support offerings Place an order for 24/7/365 Technical Support here Learn more about Pantek, who we are, and what we do Chat with a Live Operator Related httpd.apache.org Links announce bugs cvs dev docs gui-dev modproxy-dev packagers testers Request more information about Pantek

> The v2.0 cache is being designed so this either won't happen or a

Cool!

Thanks,
Kwin Received on Fri May 11 23:57:49 2001