[us...@httpd] How to specify distinct groups of Substitute patterns with mod_substitute and mod_filter, one group for one substitute provider and another group for another provider?

2010-11-03 Thread Chris Markle
Basically I have a working configuration of mod_substitute and mod_filter that always attempts substitution in text/* content. It's configured roughly like this: LoadModule substitute_module modules/mod_substitute.so LoadModule filter_module modules/mod_filter.so FilterProvider gzinflate INFLATE

Re: [us...@httpd] cannot get mod_substitute to substitute in response from remote server in reverse proxy setup

2010-10-29 Thread Chris Markle
Nick, Use mod_filter instead. Thanks for that good suggestion. I worked something up to test this with mod_filter and mod_substitute and it seems to be working. Just including my config here for the next poor sap that has this question. Thanks again... Chris * * *

[us...@httpd] what is this mod-substitute debugging output trying to tell me?

2010-10-29 Thread Chris Markle
Using mod_substitute via mod_filter and I turned on FilterLogging lvele 1. Here's what I see in the log. What's curious to me is that I haven't even got a specific substitute pattern enabled. Can anyone give me some clues as to what these log message are indicating? [Fri Oct 29 16:59:09 2010]

[us...@httpd] cannot get mod_substitute to substitute in response from remote server in reverse proxy setup

2010-10-28 Thread Chris Markle
Trying to get mod_substitute to work for me in a reverse proxy setup and having troubles, specifically the substitution in not occurring in responses from the remote server. Basically my browser clients are contacting my Apache setup at help-proxy.asperasoft.com and are being reverse proxied to

[us...@httpd] can I use Header unset X-Forwarded-Host to get rid of that header? Doesn't seem to work if so...

2010-10-27 Thread Chris Markle
My Apache fu is not strong so please keep that in mind here... I have configured Apache (2.2.16 on Centos 5) as a reverse proxy. When I proxy through this configuration to a remote HTTP server, Apache is adding X-Forwarded-For, X-Forwarded-Host and X-Forwarded-Server headers to the requests sent