This is one of the possible solutions that I was thinking. But it seems it will make the envirnoment more complex and even worse in a cluster environment. I am thinking if it is possible to do something like mod_headers. But first I need to ensure that I can read the existing headers in my own module. If the mod_headers liked approach don't work, I will try the proxy solution. Or anyone has other great alternative? Thanks On Sat, Jan 24, 2009 at 1:14 AM, Matt McCutchen <matt@xxxxxxxxxxxxxxxxx> wrote: > On Sat, 2009-01-24 at 00:09 +0800, anson ho wrote: >> I have no way to upgrade apache as the content handler (a third party >> one) only support apache 1.3. So, is there any other ways that I can >> modify the response headers that were returned from the content >> handler. I've read mod_headers but it can only do simple operation. >> What I need to do is that new headers will be created depending on >> existing headers. > > I wonder if it would work to set up a separate Apache 2.2 that proxies > to the Apache 1.3 with your third-party handler and then applies a > filter to the response headers. If no filter does what you need, I > guess you could even write your own CGI script that acts as a proxy and > modifies the headers however you like. > > -- > Matt > > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP Server Project. > See <URL:http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > > --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|