Hi all! I've got Zope installed on a Win2K Server. In that same server I've got IIS installed, which I can't uninstall because I need it for mail and other services, and IIS takes port 80. So now when I want to enter into Zope I have to write 'localhost:8080', and if I just write 'localhost' I get into IIS. I need an easy redirection of some kind that will allow me to get into IIS with 'localhost' and into Zope with 'localhost/zope' or 'zope.localhost', without the ':8080'. I've searched in zope.org, and I've tried two approaches: - http://www.zope.org/Members/brianh/iis_howto : I couldn't get it to work, and besides I've read that using pcgi makes the system unstable. - http://www.zope.org/Members/andym/ASP404 : I couldn't get it to work, and besides the author says it doesn't work in all situations. 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. So, can anyone help me do this easily? Thanks in advance, Igor Leturia
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
Dude why? Just change the Zope start script or start.bat and add -w 80 and zope will run on port 80 instead of 8080. Virtual Host Monsters couldn't be easier. ----- Original Message ----- From: "Max M" <maxm@mxm.dk> To: "Igor Leturia" <IGOR@emun.com> Cc: <zope@zope.org> Sent: Tuesday, April 09, 2002 12:09 PM 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 )
Matt Gregory wrote:
Dude why? Just change the Zope start script or start.bat and add -w 80 and zope will run on port 80 instead of 8080. Virtual Host Monsters couldn't be easier.
The bets cure for your blues is "Apache" It is much better at integrating webservers from all over the place than IIS.
He said that he needed the IIS on port 80 for mail services, so I assumed that he has some web interface to a mailserver running through the IIS regards Max M
Does he really need IIS port 80 for webmail front end ? Or does he need IIS port 25 for SMTP and doesn't know how to tell IIS not to start start IIS on port 80 ? Max M schrieb:
Matt Gregory wrote:
Dude why? Just change the Zope start script or start.bat and add -w 80 and zope will run on port 80 instead of 8080. Virtual Host Monsters couldn't be easier.
The bets cure for your blues is "Apache" It is much better at integrating webservers from all over the place than IIS.
He said that he needed the IIS on port 80 for mail services, so I assumed that he has some web interface to a mailserver running through the IIS
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 )
-> Or does he need IIS port 25 for SMTP and doesn't know how to tell IIS not to -> start start IIS on port 80 ? Eh? Does IIS handle SMTP traffic? That's news to me.
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 )
[Igor Leturia] I've got Zope installed on a Win2K Server. In that same server I've got IIS installed, which I can't uninstall because I need it for mail and other services, and IIS takes port 80. So now when I want to enter into Zope I have to write 'localhost:8080', and if I just write 'localhost' I get into IIS. I need an easy redirection of some kind that will allow me to get into IIS with 'localhost' and into Zope with 'localhost/zope' or 'zope.localhost', without the ':8080'. [Tom P] You can easily configure IIS to redirect to any particular page on Zope. For example, I have a Zope folder called "gcm", and Zope is on port 8080. I set up IIS, and created a virtual directory, also called "gcm" for IIS. The wizard for setting it up makes you point to some directory, but that does not matter because you will change it right away. Next, open the properties for that virtual folder and change it to redirect to the corresponding Zope directory. Now http://localhost:11111/gcm (the IIS virtual directory) gets transferred over to http://localhost:8080/gcm/ (my Zope installation). You would have to map each top-level folder you want people to get at through IIS. There is no need for Apache or Virtual Host Monster as long as this is all you want to do. Cheers, Tom P
Does that essentially do a redirect, rather than any sort of proxy? Hoping-there-wasnt-a-really-obvious-answer-under-my nose-ly yours -- Andy McKay
There is an IIS equivalent of Apache mod_rewrite http://www.qwerksoft.com/products/iisrewrite/ I don't have any experience with this product - it is not free anyway. -vsb
Does that essentially do a redirect, rather than any sort of proxy?
Hoping-there-wasnt-a-really-obvious-answer-under-my nose-ly yours -- Andy McKay
The rewrite bit is just one component. Its the proxy bit as well... There are a few others, but none of them free. I want a free one :) ----- Original Message ----- From: <vsbabu@vsbabu.org> To: "Andy McKay" <andy@agmweb.ca> Cc: <zope@zope.org> Sent: Tuesday, April 09, 2002 11:57 AM Subject: Re: [Zope] Zope and IIS
There is an IIS equivalent of Apache mod_rewrite
http://www.qwerksoft.com/products/iisrewrite/
I don't have any experience with this product - it is not free anyway.
-vsb
Does that essentially do a redirect, rather than any sort of proxy?
Hoping-there-wasnt-a-really-obvious-answer-under-my nose-ly yours -- Andy McKay
_______________________________________________ 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 )
[Andy McKay]
Does that essentially do a redirect, rather than any sort of proxy?
Hoping-there-wasnt-a-really-obvious-answer-under-my nose-ly yours --
Well, they __call__ it a redirect, and I didn't have to set up any proxy settings, so yes, I think it really is a redirect rather than a proxy. Also, at the browser, the url in the location display really becomes the actual Zope url after the redirect. The solution I described only redirects one exact URL, but if someone tried to enter lower down in the folder tree it wouldn't be redirected. There is supposed to be a way to handle that too (with "redirect variables", I think) , but I don't know how to do it yet. I've only had IIS installed for about an hour, though, so I don't know much. Cheers, Tom P
Thomas B. Passin wrote:
[Andy McKay]
Does that essentially do a redirect, rather than any sort of proxy?
Hoping-there-wasnt-a-really-obvious-answer-under-my nose-ly yours --
Well, they __call__ it a redirect, and I didn't have to set up any proxy settings, so yes, I think it really is a redirect rather than a proxy.
No it is a proxy!
Also, at the browser, the url in the location display really becomes the actual Zope url after the redirect
That is only if you have configured Zope wrong. You need the VirtualHosteMonster . regards Max M
[Max M]
Thomas B. Passin wrote:
[Andy McKay]
Does that essentially do a redirect, rather than any sort of proxy?
Hoping-there-wasnt-a-really-obvious-answer-under-my nose-ly yours --
Well, they __call__ it a redirect, and I didn't have to set up any proxy settings, so yes, I think it really is a redirect rather than a proxy.
No it is a proxy!
Also, at the browser, the url in the location display really becomes the actual Zope url after the redirect
That is only if you have configured Zope wrong. You need the VirtualHosteMonster .
Whatever do you mean? I haven't configured Zope at all. It was installed using the straight binary installer, with no thought of IIS in mind. It ran fine for a long time. Today I installed IIS onto Win2000 SP2. When I set up a virtual folder in IIS to redirect to the Zope installation, the url that the browser displays is in fact the one I would have typed to get to Zope directly. I run another (java) special-purpose server on port 8000. I just configured another IIS virtual folder to redirect to it. I get the same results, which shows that it has nothing to do with Zope configuration. Tell us why you think there's a proxy involved, would you? Because it sure looks like a redirect to me. Cheers, Tom P
-> Tell us why you think there's a proxy involved, would you? Because it sure -> looks like a redirect to me. I don't know anything about IIS, but there's a very simple way to answer this question. Run a packet sniffer and look for the HTTP "Location" header.
participants (9)
-
Andy McKay -
Derek Simkowiak -
Dirk Datzert -
Igor Leturia -
Lennart Regebro -
Matt Gregory -
Max M -
Thomas B. Passin -
vsbabuļ¼ vsbabu.org