Re: mod_proxy patches for HTTP Header manipulation

Kwindla Hultman Kramer wrote:

> These directives are all intended to be used as part of a

The basic problem is that by adding the code to the proxy, only the proxy can use the code. This is one of the main reasons we ripped the cache code out of mod_proxy in v2.0 - it should be possible for the whole of Apache to use a cache, not just proxy.

I just took a look at mod_headers in v2.0 - hmmmm - looks like the old mod_headers in v1.3.

In theory mod_headers in v2.0 should be a filter, not a fixup. This way potential ordering problems are solved, and the ability will exist to filter both incoming and outgoing headers from any piece of Apache (including mod_cgi, mod_proxy, etc).

I don't have a hassle with this going into the v1.3 code as is, but for v2.0 I'm keen to find the best solution to the problem within what v2.0 can do over v1.3.

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

> CacheFreshenDate, if 'On', sets the Date header to be current when a

Ok.

> ProxyResponseExpiresVector allows one to decouple the internal

So basically you are saying "this page has a TTL of <seconds>, regardless of what the backend server wanted".

> We use this to tell the world at large to cache some of our

This is because when a cached file expires, the new revalidated cached file won't be available to the rest of Apache until it has downloaded completely. This means there is a short window where all requests will go through to the backend server, until at least one download is complete, and that cached download suddenly becomes available to other processes.

The v2.0 cache is being designed so this either won't happen or a workaround will be available.

> Setting ProxyResponseExpiresVector to 30 seconds has made the

Do you need more 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

Hmmmm - all of this really belongs in mod_headers in v2.0 - I'll see what I can do to get this changed.

Regards,
Graham

-- 
-----------------------------------------
minfrin@sharp.fm		"There's a moon
					over Bourbon Street
						tonight..."