Zope/manage problem
Hello! After much struggle, I finally got Zope 2.0 working on my Mandrake 6.1b linux system. I first got it working with the Zserver, then without it (just Apache + PCGI). I had to make some accessibility changes to a couple of the files that weren't described in any of the docs (as far as I could tell), but that isn't important at the moment. So, its working, mostly... I open up Netscape, go to http://my.computers.address.org/Zope/manage, enter my superuser login and password, and voila!---I'm in the Zope manage menu. Everything seems to be working great---I can add users, objects, the works. But the buttons on the main page ([Rename] [Cut] [Copy] [Delete] [Export...]) don't work. Pressing any of them, regardless of what I've checked off in the menu, gives me a "404 Not Found" error. I've done a little diagnostics and checked out the httpd log files. Every time I press one of those buttons, the server tries to find something in /home/httpd/html/Zope. But there is no Zope file or directory in the html directory---I only have a Zope.cgi in the /home/httpd/cgi-bin directory. The log entry is as follows: [Mon Sep 13 22:33:06 1999] [error] [client 216.63.52.0] File does not exist: /home/httpd/html/Zope Has anyone else experienced this problem? I couldn't find any mention of it in the distribution docs, online faqs and guides, or in the mailing list archives. My Zope.cgi file looks like this (unchanged from what was generated by the installation precess): #!/usr/local/Zope-2.0.0/pcgi/pcgi-wrapper PCGI_NAME=Zope PCGI_MODULE_PATH=/usr/local/Zope-2.0.0/lib/python/Zope PCGI_PUBLISHER=/usr/local/Zope-2.0.0/pcgi/pcgi_publisher.py PCGI_EXE=/usr/bin/python PCGI_SOCKET_FILE=/usr/local/Zope-2.0.0/var/pcgi.soc PCGI_PID_FILE=/usr/local/Zope-2.0.0/var/pcgi.pid PCGI_ERROR_LOG=/usr/local/Zope-2.0.0/var/pcgi.log PCGI_DISPLAY_ERRORS=1 BOBO_REALM=/usr/local/Zope-2.0.0/Zope.cgi BOBO_DEBUG_MODE=1 INSTANCE_HOME=/usr/local/Zope-2.0.0 The only other change I made was the following addition to /etc/httpd/conf/httpd.conf (again, as described in the docs): # Zope configuration maps /Zope/ to the Zope.cgi PCGI script 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] Any assistance with this is greatly appreciated. Thanks, -Scott
Scott Thomas Haug wrote:
RewriteRule ^/Zope/(.*) /home/httpd/cgi-bin/Zope.cgi/$1 [e=HTTP_CGI_AUTHORIZATION:%1,t=application/x-httpd-cgi,l]
It's a subtle, yet infuriating bug in the rewrite rule. When you manage your root, you're producing URLs like 'host:port/Zope?manage...'. Note the lack of a slash after 'Zope'. Try replacing '^/Zope/(.*)' with '^/Zope(.*)'
On Tue, 14 Sep 1999, Evan Simpson wrote:
Scott Thomas Haug wrote:
RewriteRule ^/Zope/(.*) /home/httpd/cgi-bin/Zope.cgi/$1 [e=HTTP_CGI_AUTHORIZATION:%1,t=application/x-httpd-cgi,l]
It's a subtle, yet infuriating bug in the rewrite rule. When you manage your root, you're producing URLs like 'host:port/Zope?manage...'. Note the lack of a slash after 'Zope'. Try replacing '^/Zope/(.*)' with '^/Zope(.*)'
Will this work? I would think that by using Zope(.*) the Zope.cgi/$1 would expand wrongly (although I have not tried it, it would expand I'm guessing to an extra '/' character, giving a double-/, which may not be a problem??) I've yet to need to address this problem, but can see it heading my way.. ------------------------------------------------------------ Stuart Woolford, stuartw@newmail.net Unix Consultant. Software Developer. Supra Club of New Zealand. ------------------------------------------------------------
I also had trouble with this and removing the slash works perfectly (at least for me). There doesn't seem to be any rhyme or reason to this, for example I have to have different RewriteRules on two machine which to all intents and purposes are identical :¬| Anyway, give a try and it'll work a dream. HTH Phil phil@philh.org ----- Original Message ----- From: Stuart Woolford <stuartw@newmail.net> To: Evan Simpson <evan@4-am.com>; <sth2@cs.wustl.edu> Cc: <zope@zope.org> Sent: Tuesday, September 14, 1999 8:45 AM Subject: Re: [Zope] Zope/manage problem
On Tue, 14 Sep 1999, Evan Simpson wrote:
Scott Thomas Haug wrote:
RewriteRule ^/Zope/(.*) /home/httpd/cgi-bin/Zope.cgi/$1 [e=HTTP_CGI_AUTHORIZATION:%1,t=application/x-httpd-cgi,l]
It's a subtle, yet infuriating bug in the rewrite rule. When you manage your root, you're producing URLs like 'host:port/Zope?manage...'. Note the lack of a slash after 'Zope'. Try replacing '^/Zope/(.*)' with '^/Zope(.*)'
Will this work? I would think that by using Zope(.*) the Zope.cgi/$1 would expand wrongly (although I have not tried it, it would expand I'm guessing to an extra '/' character, giving a double-/, which may not be a problem??)
I've yet to need to address this problem, but can see it heading my way.. ------------------------------------------------------------ Stuart Woolford, stuartw@newmail.net Unix Consultant. Software Developer. Supra Club of New Zealand. ------------------------------------------------------------
_______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope
(To receive general Zope announcements, see: http://www.zope.org/mailman/listinfo/zope-announce
For developer-specific issues, zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )
Many thanks! It *did* work like a dream. I appreciate all of your prompt and curteous responses. -Scott On Tue, 14 Sep 1999, Phil Harris wrote:
I also had trouble with this and removing the slash works perfectly (at least for me).
There doesn't seem to be any rhyme or reason to this, for example I have to have different RewriteRules on two machine which to all intents and purposes are identical :¬|
Anyway, give a try and it'll work a dream.
HTH
Phil phil@philh.org
----- Original Message ----- From: Stuart Woolford <stuartw@newmail.net> To: Evan Simpson <evan@4-am.com>; <sth2@cs.wustl.edu> Cc: <zope@zope.org> Sent: Tuesday, September 14, 1999 8:45 AM Subject: Re: [Zope] Zope/manage problem
On Tue, 14 Sep 1999, Evan Simpson wrote:
Scott Thomas Haug wrote:
RewriteRule ^/Zope/(.*) /home/httpd/cgi-bin/Zope.cgi/$1 [e=HTTP_CGI_AUTHORIZATION:%1,t=application/x-httpd-cgi,l]
It's a subtle, yet infuriating bug in the rewrite rule. When you manage your root, you're producing URLs like 'host:port/Zope?manage...'. Note the lack of a slash after 'Zope'. Try replacing '^/Zope/(.*)' with '^/Zope(.*)'
Will this work? I would think that by using Zope(.*) the Zope.cgi/$1 would expand wrongly (although I have not tried it, it would expand I'm guessing to an extra '/' character, giving a double-/, which may not be a problem??)
I've yet to need to address this problem, but can see it heading my way.. ------------------------------------------------------------ Stuart Woolford, stuartw@newmail.net Unix Consultant. Software Developer. Supra Club of New Zealand. ------------------------------------------------------------
_______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope
(To receive general Zope announcements, see: http://www.zope.org/mailman/listinfo/zope-announce
For developer-specific issues, zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )
participants (4)
-
Evan Simpson -
Phil Harris -
Scott Thomas Haug -
Stuart Woolford