Ian Holsman wrote: >> and have noticed that my reverse proxies are getting 403'd. (where they were >> working fine >> last time)
>One thing that I have found to be a brilliant tool for debugging these >sorts of things is a program called tcpflow. It records tcp connections, >and saves them in files (or outputs them to the console). It's really >useful for finding out exactly who is saying what to what. sounds good. >> what do you guys think of adding a hook (like mod-include has) where people >> could register a function to >> add extra headers to the r-proxy call? >Hmmm - this is an interesting one. There is the output filter chain, >which can have filters added to it (which could add headers, or do other >things). There is also the backend filter chain, which handles >communication with the backend - and currently you cannot add external >filters to it. I'll try look at this this and see what I can come up >with... Ok.. the reason is the following. we plan on adding info to the notes table to set up things like Language, Locale, and if the request is a robot/spider (and some other stuff). we need to pass this to our application server, as extra header fields (simmilar to the X-Forwarded one ) the other thing we need for logging is when a redirect on the app-server gets done, we need to set some notes saying where they got redirected to. the problem with filters for the first part would be that I would have to write 2 modules. one a content handler (which would do the setting of the notes based on the incoming header, or setting of the notes from things like mod_include) and one a filter which could add the stuff to the proxied header. ..Ian >Regards, >Graham >------------------------------------------- >[EMAIL PROTECTED] "There's a moon >over Bourbon Street >tonight..." -- Ian Holsman Performance Measurement & Analysis 415-364-8608
