Ian Holsman wrote:
before you commit the change to 2.0 can you make sure that the existing behavior is still maintained/available, and if it can't be then you will need to make a new directive.
There is no change that I can see to existing behaviour (there was no previous sane behaviour for ProxyPassReverse http://blah/ http://foo/)
also.. what about virtual hosts.. doesn't requiring them to have a hostname break them?
There is no requirement to have a hostname - the old behaviour still holds.
Regards,
Graham
--
-----------------------------------------
[EMAIL PROTECTED] "There's a moon
over Bourbon Street
tonight..."
