[Zope-dev] bug in VirtualHostMonster in 2.5.0
Hi guys, I bring to your attention the bug 235:http://collector.zope.org/Zope/235 in the Zope collector, which I just posted. Apparently VHM is inserting exactly one spurious '/' in urls when the _vh_folder syntax is used. The problem seems to be in the VirtualHostMonster.__call__ method at lib/python/Products/SiteAccess/VirtualHostMonster.py, which has changed a lot relative to the 2.4.x version, however I couldn't make head or tails of that algorithm, so I wouldn't know how to fix it. This problem is seriously hampering our deployment of Zope 2.5.0 on clients, since most of the time we publish the root of the site from a Zope Folder and need the _vh_folder syntax to access the real Zope root for manteinance. Cheers, Leo PS: since we're talking about the collector, I'll also plug the other but I posted there http://collector.zope.org/Zope/167;, which talks about a problem with SuperFind() and includes a simple fix. It's still pending... -- Ideas don't stay in some minds very long because they don't like solitary confinement. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: bug in VirtualHostMonster in 2.5.0
Ok, I think I found a fix for it, but it's not a change in VHM.
As I mentioned in a follow-up to Zope bug 235, there is an inconsistency
in lib/python/ZPublisher/HTTPRequest.py in HTTPRequest.setVirtualRoot()
The attached patch (also in the bug report) explains what this
inconsistency is and seems to fix the VHM problem, but I don't know what
other side-effects it has. The 'utilities/testrunner.py -a' seems to run
ok.
On Wed, 2002-02-20 at 16:29, Leonardo Rochael Almeida wrote:
Hi guys,
I bring to your attention the bug
235:http://collector.zope.org/Zope/235 in the Zope collector, which I
just posted.
Apparently VHM is inserting exactly one spurious '/' in urls when the
_vh_folder syntax is used. The problem seems to be in the
VirtualHostMonster.__call__ method at
lib/python/Products/SiteAccess/VirtualHostMonster.py, which has changed
a lot relative to the 2.4.x version, however I couldn't make head or
tails of that algorithm, so I wouldn't know how to fix it.
This problem is seriously hampering our deployment of Zope 2.5.0 on
clients, since most of the time we publish the root of the site from a
Zope Folder and need the _vh_folder syntax to access the real Zope root
for manteinance.
Cheers, Leo
PS: since we're talking about the collector, I'll also plug the other
but I posted there http://collector.zope.org/Zope/167;, which talks
about a problem with SuperFind() and includes a simple fix. It's still
pending...
--
Ideas don't stay in some minds very long because they don't like
solitary confinement.
--- HTTPRequest.py.orig Wed Feb 20 19:14:20 2002
+++ HTTPRequest.py Wed Feb 20 19:16:00 2002
@@ -158,7 +158,8 @@
Treat the current publishing object as a VirtualRoot
other = self.other
if type(path) is type(''):
-path = filter(None, path.split( '/'))
+path = path.split('/')
+path = filter(None, path)
self._script[:] = map(quote, path)
del self._steps[:]
parents = other['PARENTS']
Re: [Zope-dev] Re: bug in VirtualHostMonster in 2.5.0
What info can you get from dtml-var REQUEST , say in a dtml doc called env_test ?? eg: ServerName newsite ProxyPass / http://192.168.X.Y:8080/VirtualHostBase/http/newsite:80/newsite/VirtualHostRoot/ ProxyPassReverse / http://192.168.X.Y:8080/VirtualHostBase/http/newsite:80/newsite/VirtualHostRoot/ ProxyPass /misc_ http://192.168.X.Y:8080/misc_ ProxyPass /p_ http://192.168.X.Y:8080/p_ yields: PATH_INFO '/VirtualHostBase/http/newsite:80/newsite/VirtualHostRoot/env_test' and PATH_TRANSLATED '/VirtualHostBase/http/newsite:80/newsite/VirtualHostRoot/env_test' ProxyPass /newsite http://192.168.X.Y:8080/VirtualHostBase/http/newsite:80/newsite/VirtualHostRoot/_vh_newsite/ ProxyPassReverse /newsite http://192.168.X.Y:8080/VirtualHostBase/http/newsite:80/newsite/VirtualHostRoot/_vh_newsite/ ProxyPass /misc_ http://192.168.X.Y:8080/misc_ ProxyPass /p_ http://192.168.X.Y:8080/p_ yields PATH_INFO '/VirtualHostBase/http/newsite:80/newsite/VirtualHostRoot/_vh_newsite//env_test' and PATH_TRANSLATED '/VirtualHostBase/http/newsite:80/newsite/VirtualHostRoot/_vh_newsite/env_test' The above is how it works on Zope 2.4.3 I remember the second example being a pain to get working on 2.4.3, I think ZMI needed the extra trailing / on the proxypass statement in order to work right. Adam At 08:02 PM 2/20/2002 -0300, Leonardo Rochael Almeida wrote: Ok, I think I found a fix for it, but it's not a change in VHM. As I mentioned in a follow-up to Zope bug 235, there is an inconsistency in lib/python/ZPublisher/HTTPRequest.py in HTTPRequest.setVirtualRoot() The attached patch (also in the bug report) explains what this inconsistency is and seems to fix the VHM problem, but I don't know what other side-effects it has. The 'utilities/testrunner.py -a' seems to run ok. On Wed, 2002-02-20 at 16:29, Leonardo Rochael Almeida wrote: Hi guys, I bring to your attention the bug 235:http://collector.zope.org/Zope/235 in the Zope collector, which I just posted. Apparently VHM is inserting exactly one spurious '/' in urls when the _vh_folder syntax is used. The problem seems to be in the VirtualHostMonster.__call__ method at lib/python/Products/SiteAccess/VirtualHostMonster.py, which has changed a lot relative to the 2.4.x version, however I couldn't make head or tails of that algorithm, so I wouldn't know how to fix it. This problem is seriously hampering our deployment of Zope 2.5.0 on clients, since most of the time we publish the root of the site from a Zope Folder and need the _vh_folder syntax to access the real Zope root for manteinance. Cheers, Leo PS: since we're talking about the collector, I'll also plug the other but I posted there http://collector.zope.org/Zope/167;, which talks about a problem with SuperFind() and includes a simple fix. It's still pending... -- Ideas don't stay in some minds very long because they don't like solitary confinement. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] Memory Problem with 2.3.3
Hi, I have a problem with my Zope 2.3.3 running on a redhat immunix 6.2. The problem is that the zope-threads are growing up. I have running a top since yesterday. 2 days ago the size of all zope-processes was 44MB, yesterday it was 54MB today it is 64MB. This means to me, that all threads are growing up 10MB a day. If have also looked in the debug-information at the top-refcounts. OFS.Image.Image has a delta of around +1500... Is there a problem with OFS.Image.Image, are these objects never closed Please Help Regards, -- Andre SchubertEMail: [EMAIL PROTECTED] Tel: 03774 6625-78 km3 teledienst GmbH Fax: 03774 6625-79 ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
