Hi, Gitte Wange wrote:

On 26 Mar 2001 13:26:51 +0100, Mayers, Philip J wrote:

...

1) Do you have this in your Apache config (or something like it):

RewriteEngine on RewriteCond %{HTTP:Authorization} ^(.*) RewriteRule ^/Zope(.*) /home/httpd/cgi-bin/Zope.cgi$1 [e=HTTP_CGI_AUTHORIZATION:%1,t=application/x-httpd-cgi,l]

Yes this is entered in a <VirtualHost> directiv in my httpd.conf

[...]

Anyone else how can help ?

If you still have ZServer listening on port 8080 (it normally is, if not disabled by -w , as I've learned just a few days ago :-) ), you could try to reach your management I/F directly on this port. At least you can determine, wether the error is on the Zope side or with your Apache setup. If that works, I could send you my rewrite rules, if you'd need them. mailx, ta -------------------------------------------------------------------------- smartferret it-consulting Dipl.-Ing. Linzbichler KEG Dipl.-Ing. Takashi Veikko Linzbichler Tannhofweg 28/3 A-8044 Graz, Austria Tel.: 0316 / 39 89 40 -0 Fax: 0316 / 39 89 40 -20 Mobil: 0676 / 31 26 286 eMail: takashi.linzbichler@smartferret.com WWW: http://www.smartferret.com --------------------------------------------------------------------------

Hi, --On Montag, 26. März 2001 14:04 +0200 Gitte Wange <gitte@mmmanager.org> wrote:

...

If you still have ZServer listening on port 8080 (it normally is, if not disabled by -w , as I've learned just a few days ago :-) ), you could try to reach your management I/F directly on this port. At least you can determine, wether the error is on the Zope side or with your Apache setup.

Okay this was very interesting: When I tried to enter http://<my.ipnumber>:8080/manage, I got an error saying that the connection was refused by the server either because the server was busy (whick I know it isn't) or becuase the server may not be accepting connections.

I guess it's a zope problem - any who can help ?

Hm, I don't know your OS environment ... But what I'd try is: 1) Check, id Zope is really running (with Linux: ps aux |grep z2) 2) Check Zope's startup params 3) If on a Linux box: Do you have any ipchains-rules or similar running ? If nothing else seems to help, I'd advise to first get Zope running standalone and then switch to an setup behind Apache. hth, ta -------------------------------------------------------------------------- smartferret it-consulting Dipl.-Ing. Linzbichler KEG Dipl.-Ing. Takashi Veikko Linzbichler Tannhofweg 28/3 A-8044 Graz, Austria Tel.: 0316 / 39 89 40 -0 Fax: 0316 / 39 89 40 -20 Mobil: 0676 / 31 26 286 eMail: takashi.linzbichler@smartferret.com WWW: http://www.smartferret.com --------------------------------------------------------------------------

--On Montag, 26. März 2001 14:39 +0200 Gitte Wange <gitte@mmmanager.org> wrote:

...

1) Check, id Zope is really running (with Linux: ps aux |grep z2)

Output from ps -aux: #101 3383 0.0 0.4 12108 620 ? S 09:33 0:10 /usr/bin/python z2.py So it is running..

Could it be, you've got an user conflict between Apache and Zope ? At least my setup only works, when startinng Zope with -u wwwrun which is the user Apache is running as. ta -------------------------------------------------------------------------- smartferret it-consulting Dipl.-Ing. Linzbichler KEG Dipl.-Ing. Takashi Veikko Linzbichler Tannhofweg 28/3 A-8044 Graz, Austria Tel.: 0316 / 39 89 40 -0 Fax: 0316 / 39 89 40 -20 Mobil: 0676 / 31 26 286 eMail: takashi.linzbichler@smartferret.com WWW: http://www.smartferret.com --------------------------------------------------------------------------

--On Montag, 26. März 2001 14:56 +0200 Gitte Wange <gitte@mmmanager.org> wrote:

Well I just accomplished to start Zope on http://<my.ip>:8080/manage Now .. is it possible to access zope on http://<my.ip>/manage ??

OK. That's what I got in my httpd.conf. But beware, I've got no virtual hosting, although AFAIK there's not much difference, you just put the statements into the respective virtual host sections. --- snip --- ScriptAlias /zope-cgi-bin/ "/usr/local/httpd/zope-cgi-bin/" <Directory "/usr/local/httpd/zope-cgi-bin"> AllowOverride None Options None Options +ExecCGI Order allow,deny Allow from all </Directory> --- snap --- --- snip --- RewriteEngine on # REwriteEngine Off RewriteLog /var/log/httpd_rewrite RewriteLogLevel 2 # # first we check for ~user homes ... # if not done here, we'd crash into the 'static' rule :-) RewriteRule ^/~(.*) /~$1 [PT] UserDir public_html # we serve 'standard cgi' as usual RewriteRule ^/cgi-bin/(.*) /usr/local/httpd/cgi-bin/$1 [e=HTTP_CGI_AUTHORIZATION:%1,t=application/x-httpd-cgi,l] # next is for Zope RewriteCond %{HTTP:Authorization} ^(.*) RewriteRule ^/zope/(.*) /usr/local/httpd/zope-cgi-bin/Zope.cgi/$1 [e=HTTP_CGI_AUTHORIZATION:%1,t=application/x-httpd-cgi,l] # we serve static content in DocRoot (not as described in HOWTO !!!) RewriteRule ^(.*) /usr/local/httpd/htdocs/$1 [l] # --- snap --- Actually the RewriteRules might need some explanantion: 1) You don't need the first rule unless serving static (i.e. non-Zope) user-sites (something like http://your_server/~your_user 2) You might as well not need the 'standard cgi' rule 3) If you do it that way, all Zope content is served hrough http://your_server/zope/rest_of_url, all non-Zope content through http://your_server/what_so_ever But you can easily change this by altering the last two rules, for example, have a /static/ directory for non-Zope content as serving your Zope site through the base-url (you'll need the 'Zope-rule' as the last one in this case, since it covers any URL that made its way to that rule ...) hth, ta -------------------------------------------------------------------------- smartferret it-consulting Dipl.-Ing. Linzbichler KEG Dipl.-Ing. Takashi Veikko Linzbichler Tannhofweg 28/3 A-8044 Graz, Austria Tel.: 0316 / 39 89 40 -0 Fax: 0316 / 39 89 40 -20 Mobil: 0676 / 31 26 286 eMail: takashi.linzbichler@smartferret.com WWW: http://www.smartferret.com --------------------------------------------------------------------------