The bets cure for your blues is "Apache" It is much better at integrating webservers from all over the place than IIS.
Using Apache is not a helpful answer, one day people will stop saying just use Unix / Mozilla (insert non Microsoft solution here). Some people have to use IIS. Those choices mentioned are your methods at present. There is rumour of an ISAPI filter in progress that will solve this. If you are an ISAPI expert we would love some help on the project. Otherwise you'll have to wait... ----- Original Message ----- From: "Max M" <maxm@mxm.dk> To: "Igor Leturia" <IGOR@emun.com> Cc: <zope@zope.org> Sent: Tuesday, April 09, 2002 9:09 AM Subject: Re: [Zope] Zope and IIS
Igor Leturia wrote:
I'm quite desperate, I need this urgently! It's not just that the ':8080' makes the adress ugly, it's also that the website cannot be accessed from many companies where they've got a firewall that blocks access to the outside from any port different to 80.
I've also heard something about 'rewrite rules', 'virtual host monsters', 'redirections', but I know nothing about them.
The bets cure for your blues is "Apache" It is much better at integrating webservers from all over the place than IIS.
You need to install Apcahe on port 80, Zope on port 8080 and move IIS to port 81
Then you can talk to both your Zope and IIS through the Apache at port 80 using rewrite rules. From the outside alle three servers will seem like one. A dedicated webserver with 256 MB of ram should handle it nicely. 128 MB might be enough.
I have is set up and it's not that difficult.
regards Max M
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )