>From: "Steve Bush" <[EMAIL PROTECTED]>
> This required that I dedicate web services
> on the SME box to WebSphere.
> Being able to ProxyPass on a virtual host,
> ie websphere.bushinc.com, would be a
> more ideal setup in this situation.
> It would also be helpful to be able to
> ProxyPass the root without manually
> modifying the httpd.conf file.
Yes, that matches my sentiments almost exactly.
I've worked around it for the moment with a
more drastic manual configuration, adding another
IP address to support a manually configured instance
of httpd where the VirtualHost definitions won't be
overwritten by the SME version. This took a few
changes to the masq ipchain filters as well.
The other suggestion I have after doing this (besides
moving the ProxyPass generation into the VirtualHost
sections) is to allow multiple ServerAliases to be
configured within a <VirtualHost > section. In this
particular case I wanted the proxied site to appear
in several different domains and adding ServerAliases
seems a lot neater than having to repeat the definition
for each name. Plus, you may or may not want the
side effects of accepting mail (etc.) that you get if you
have to specify each Virtual host name at the SME
config level.
It would also be useful for some similar situations
to have a way to make the SME configuration set
AllowOverride All
in specified ibays. This would allow many customizations
to be done with appropriate commands in a .htaccess file.
You can't use ProxyPass there, but it might be possible to
accomplish the same thing with a RewriteRule with the [p] flag.
Les Mikesell
[EMAIL PROTECTED]
--
Please report bugs to [EMAIL PROTECTED]
Please mail [EMAIL PROTECTED] (only) to discuss security issues
Support for registered customers and partners to [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
