Daniël Mantione wrote:
Again, a practical situation: How many PHP packages support such headers? (Even OpenACS doesn't support them, so you would have to fix OpenACS too.) Can you (socially) convince those users to rewrite the PHP apps for you to use your OpenACS?
As a practical solution, if you needed to do it transparently you'd install a trivial C module to patch the request_rec or Conn and change the peer address to the value given in the proxy header. PHP or OACS wouldn't know the difference. In apache if you have mod_perl installed this is very easy (the C module boilerplace would be 5x the size of the actual code for the module). As for AS, I believe this was done in one or more of the old proxy modules; I don't know offhand exactly what it would be but I'm confident its not at all difficult.
What you say about the social problem is very true of course - it takes a whole lot of technical wizardry to overcome the inertia of "I don't know that system."
-J -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
