bruce@perens.com writes:
Evan Simpson sent me a fix for publishing a sub-folder, and I have ported that fix to 2.0.0a3 . Do not apply this patch naively, I've tested it once and I'm not at all familliar with the internals of Zope. It's posted here for discussion.
Wow, two different patches in the same day that fix the same problem! Both patches take the same approach, droping a certain number of pathname elements off of the request. I think this would also fit in well with Scott from Codit's multple Zope patch... Scott? Do you have an opinion on what should be done? I also like the idea of storing this information in the PCGI resource file (Zope.cgi), so as not to clutter up the rewrite rule, whose only true purpose is to fake out Apache on the HTTP Authorization header. -Michel
On 1 Jul 1999 michel@digicool.com wrote:
bruce@perens.com writes:
Evan Simpson sent me a fix for publishing a sub-folder, and I have ported that fix to 2.0.0a3 . Do not apply this patch naively, I've tested it once and I'm not at all familliar with the internals of Zope. It's posted here for discussion.
Wow, two different patches in the same day that fix the same problem! Both patches take the same approach, droping a certain number of pathname elements off of the request. I think this would also fit in well with Scott from Codit's multple Zope patch... Scott? Do you have an opinion on what should be done?
This feels like the right approach. I don't like using enviroment variables, personal hang-up I guess, but I can't think of another way around it.
I also like the idea of storing this information in the PCGI resource file (Zope.cgi), so as not to clutter up the rewrite rule, whose only true purpose is to fake out Apache on the HTTP Authorization header.
We only use one Zope.cgi file that contatins only the common information. i.e SOFTWARE_HOME etc... We use SetEnv calls inside the <virtualhost> tags to specifie things like INSTANCE_HOME and PCGI_PID_FILE. This way we do not have to have 20+ pcgi conf files floating around. P.S. If you want to make your ReWrite rule aesthetically pleasing I'd recomend using SetEnv for setting static enviroment variables. --------------------------------------------------- - Scott Robertson Phone: 714.972.2299 - - CodeIt Computing Fax: 714.972.2399 - - http://codeit.com - ---------------------------------------------------
participants (2)
-
michel@digicool.com -
Scott Robertson