Re: [Zope-dev] zope and python compatibility
I would strongly recommend using python version 2.1.3 for Zope 2.5.1 - 2.6.x and python = 2.2.2 for Zope 2.6.x. Adam On Thu, 2003-01-09 at 12:06, Tena Sakai wrote: Greetings zope-dev folks, Please help me out. I have seen below via google search: Zope 2.5 + Python 2.1 -- Good Zope 2.6 + Python 2.1 -- Good Zope 2.7 + Python 2.1 -- Bad Zope 2.5 + Python 2.2 -- Bad Zope 2.6 + Python 2.2 -- Bad Zope 2.7 + Python 2.2 -- Good This article/note was from September, 2002. Can someone please comment if the data above is still valid? Thank you. Tena Sakai ([EMAIL PROTECTED]) ___ 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 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] dupe column names not supported (Shared.DC.ZRDB) ?
Hi there, I'm currently testing (documenting, building RPM packages for) the following configuration: RedHat 8.0 python 2.1.3 postgresql 7.3 mx 2.0.3 psycopg 1.1 Zope-2.6.1b1 Having just got all the packages built and installed, I thought I'd run the database adapter, Zope and postgres through their paces starting with the SQL examples at: http://www.postgresql.org/idocs/index.php?tutorial-sql.html I ran into trouble with: http://www.postgresql.org/idocs/index.php?tutorial-join.html specifically with: SELECT W1.city, W1.temp_lo AS low, W1.temp_hi AS high, W2.city, W2.temp_lo AS low, W2.temp_hi AS high FROM weather W1, weather W2 WHERE W1.temp_lo W2.temp_lo AND W1.temp_hi W2.temp_hi; Error, exceptions.ValueError: Duplicate column name, city Traceback (innermost last): Module ZPublisher.Publish, line 98, in publish Module ZPublisher.mapply, line 88, in mapply Module ZPublisher.Publish, line 39, in call_object Module Shared.DC.ZRDB.Connection, line 115, in manage_test Module Shared.DC.ZRDB.Results, line 52, in __init__ ValueError: Duplicate column name, city Obviously this will work if you change the query to: SELECT W1.city AS city1, W1.temp_lo AS low1, W1.temp_hi AS high1, W2.city AS city2, W2.temp_lo AS low2, W2.temp_hi AS high2 FROM weather W1, weather W2 WHERE W1.temp_lo W2.temp_lo AND W1.temp_hi W2.temp_hi; City1 Low1 High1 City2 Low2 High2 San Francisco 43 57 San Francisco 46 50 Hayward 37 54 San Francisco 46 50 I did a little digging to see if the above is valid SQL92 syntax, or just uses a PostgreSQL specific extension, the only things I found: In: http://www.postgresql.org/idocs/index.php?sql-select.html In the SQL92 standard, the optional keyword AS is just noise and can be omitted without affecting the meaning. The PostgreSQL parser requires this keyword when renaming output columns because the type extensibility features lead to parsing ambiguities in this context. AS is optional in FROM items, however. And In: http://manuals.sybase.com/onlinebooks/group-as/asg1150e/mig_gde/@Generic__BookTextView/4167 Correlation Names ANSI requires correlation names on self-joins. The following query is now invalid: select columns from table1, table1 where clause ... This query must be rewritten as: select columns from table1 t1, table1 t2 where clause ... Trying it without the noise in psql: testdb1= SELECT W1.city, W1.temp_lo, W1.temp_hi, testdb1- W2.city, W2.temp_lo, W2.temp_hi testdb1- FROM weather W1, weather W2 testdb1- WHERE W1.temp_lo W2.temp_lo testdb1- AND W1.temp_hi W2.temp_hi; city | temp_lo | temp_hi | city | temp_lo | temp_hi ---+-+-+---+-+- San Francisco | 43 | 57 | San Francisco | 46 | 50 Hayward | 37 | 54 | San Francisco | 46 | 50 (2 rows) testdb1= The question: If the above example query is valid ANSI SQL92, do we aim to support it? Adam ___ 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 )
Re: [Zope-dev] dupe column names not supported (Shared.DC.ZRDB) ?
Just for curiousity, what is the use case for returning multiple columns with the same name? Sounds dubious to me. A self join will return multiple columns with the same name unless AS keyword is used. The use of AS keyword is supposed to be optional. Assuming that a user does use AS, labeling of the returned columns will be at the discretion of the user, and therefore again not guaranteed to be unique. I would guess that if Zope assumes that column names are unique, changing that assumption now would be a major p.i.t.a. :-) Adam ___ 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] python 2.1.3 on RedHat 8.0
I am working on spec/RPM for Zope 2.6.x, but obviously a working
python2.1.3 install is a pre-req if I want to support RH8.0 with the
Zope RPMS :-)
Attached are the changes made to the spec so that the python 2.1.3 SRPM
from python.org would --rebuild nicely on RedHat 8.0
Changes:
Made tools optional
Used %{__prefix}/lib/python2.1/Tools instead of tools.files for
tools sub-package.
Removed BuildPrereq for db1-devel. No longer included in RH8
(see: http://www.redhat.com/software/linux/technical/packages.html)
I don't have a RH7.x box to test on anymore.. (should have kept one of
my dev boxes at 7.x...) could someone please test the below on
RedHat 7.2 and/or 7.3?
-
To build the source RPM as a NON ROOT user
Create necessary directories in your home directory:
mkdir $HOME/rpm
mkdir $HOME/rpm/SOURCES
mkdir $HOME/rpm/SPECS
mkdir $HOME/rpm/BUILD
mkdir $HOME/rpm/SRPMS
mkdir $HOME/rpm/RPMS
mkdir $HOME/rpm/RPMS/i386
Tell RPM to use your private rpm/ tree:
echo %_topdir $HOME/rpm $HOME/.rpmmacros
Install the source RPM:
rpm -Uvh python2.1-2.1.3-1.src.rpm
Patch the spec file
cd $HOME/rpm/SPECS
patch -p0 /path_to_attached/python2.1.spec.10-22.patch
Build:
rpmbuild -ba --without tkinter python-2.1.spec
Install:
su -l
rpm -Uvh ~yourusername/rpm/RPMS/i386/python2.1*.rpm
exit
Test:
python2.1 /usr/lib/python2.1/test/regrtest.py
I got:
128 tests OK.
13 tests skipped:
-
Adam
--- python-2.1.spec 2002-04-10 00:24:47.0 -0400
+++ python-2.1.spec.10-22 2002-10-22 16:24:36.0 -0400
@@ -31,6 +31,9 @@
%define config_tkinter 1
%{?_without_tkinter: %{expand: %%define config_tkinter 0}}
+%define config_tools 1
+%{?_without_tools: %{expand: %%define config_tools 0}}
+
%define config_pymalloc --without-pymalloc
%{?_with_pymalloc: %{expand: %%define config_pymalloc --with-pymalloc}}
@@ -49,7 +52,7 @@
Patch2: Python-2.1-expat.patch
BuildRoot: /var/tmp/%{name}-%{version}-root
BuildPrereq: expat-devel = 1.1-3tummy
-BuildPrereq: db1-devel
+#BuildPrereq: db1-devel
BuildPrereq: gdbm-devel
Prefix: %{__prefix}
Packager: Sean Reifschneider [EMAIL PROTECTED]
@@ -324,5 +327,8 @@
%{__prefix}/lib/python2.1/lib-dynload/_tkinter.so*
%endif
-%files -f tools.files tools
+%if %{config_tools}
+%files tools
%defattr(-,root,root)
+%{__prefix}/lib/python2.1/Tools
+%endif
[Zope-dev] regression testing python install
Slightly of topic I know, but I thought someone here might know... I'm tweaking the python2.1 SRPM from python.org to get it to play nice with RedHat 8.0. Now that I have it compiling nicely, I thought it would be a good idea to fully regression test the resulting python install, especially as we now build with gcc 3.2 on 8.0 :-) Is there a simple way to thoroughly regression test a python install? Adam ___ 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 )
Re: [Zope-dev] Zope RPMs/debs and Linux FHS
Looks good,
I was planning to start from scratch with building a RPM for 2.6
that would work on at least RedHat 8.x AND 7.x.. Coincidentally,
this is something I planned to start on tomorrow! :-)
Instead, I'll take a few hours tomorrow to test your spec on
RedHat 8.0, it would be *really* good if this could be the basis
of and future 2.6 / 2.7 packaging efforts...
- anybody has opinions on the packaging layout. Why is it advantageous
to have many packages rather than one?
Zope, Zope-zserver and Zope-PCGI packages seem like a good idea.
Most RPM dists seem to have at least a -server sub package if they
provide a daemon (eg postgresql). Init scripts, the data dir, etc
all go in the -server subcomponent
[adam@blackbox adam]$ rpm -qa | grep postgresql
postgresql-7.2.2-1
postgresql-server-7.2.2-1
postgresql-libs-7.2.2-1
[adam@blackbox adam]$ rpm -ql postgresql-server
/etc/rc.d/init.d/postgresql
/usr/bin/initdb
/usr/bin/initlocation
/usr/bin/ipcclean
/usr/bin/pg_ctl
/usr/bin/pg_passwd
/usr/bin/postgres
/usr/bin/postmaster
/usr/lib/pgsql
/usr/lib/pgsql/backup
/usr/lib/pgsql/backup/pg_dumpall_new
/usr/lib/pgsql/plpgsql.so
/usr/share/locale/cs/LC_MESSAGES/postgres.mo
/usr/share/locale/de/LC_MESSAGES/postgres.mo
/usr/share/locale/hu/LC_MESSAGES/postgres.mo
/usr/share/locale/ru/LC_MESSAGES/postgres.mo
/usr/share/locale/zh_CN/LC_MESSAGES/postgres.mo
/usr/share/locale/zh_TW/LC_MESSAGES/postgres.mo
/usr/share/man/man1/initdb.1.gz
/usr/share/man/man1/initlocation.1.gz
/usr/share/man/man1/ipcclean.1.gz
/usr/share/man/man1/pg_ctl.1.gz
/usr/share/man/man1/pg_passwd.1.gz
/usr/share/man/man1/postgres.1.gz
/usr/share/man/man1/postmaster.1.gz
/usr/share/pgsql
/usr/share/pgsql/pg_hba.conf.sample
/usr/share/pgsql/pg_ident.conf.sample
/usr/share/pgsql/postgres.bki
/usr/share/pgsql/postgres.description
/usr/share/pgsql/postgresql.conf.sample
/var/lib/pgsql
/var/lib/pgsql/.bash_profile
/var/lib/pgsql/backups
/var/lib/pgsql/data
- anybody has any opinions of where Zope files distributed via RPMs and
debs should really go, especially wrt to the Linux FHS. I'm not sure
there is a right answer, but I don't know beans about this, so I
figure I'll ask. A file named 'Zope.spec.in' is attached to this
email which is the input file to create a Zope RPM spec file during
the make process, to give a better idea of how this works.
AFAIK on RedHat /opt or mixed in (/usr/bin etc) is fine, the argument
goes if RPM tracks all the files for you, why use /usr/local or /opt?
/opt is used too, the only problem being that it isn't often created
separate from the / partition, so there often isn't alot of space
there!
One trick to note is for creating the inituser (from 2.5.1):
# Declare the Superuser of the Default Zope Project
rm $RPM_BUILD_ROOT/usr/share/zope/inituser
%{PYTHONAPP} $RPM_BUILD_ROOT/usr/bin/zpasswd -u admin -p 123
$RPM_BUILD_ROOT/var/zope/inituser
chmod 0640 $RPM_BUILD_ROOT/var/zope/inituser
Adam
___
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 )
Re: [Zope-dev] Slow zope on windows 2000?
I'm not sure that is the case you know. Oracle 9i Linux is faster on my Linux Athlon 800 than the same release on my Win2k Dual Piii 1GHz. Also my Win box has 1Gb ram, while my Linux box has only 512Mb... In other news Apache is reported to run faster on Linux that Win2000, as is PostgreSQL. Samba is reported to provide double the throughput of Win2000 native file services, with half the response delay for client requests. Very much so! On a Win2k with Dual P3 1Ghz Zope runs slower than the same install on a Linux box with 1 P133 (I have tested this on multiple different configurations and every time it comes out the same) This, however, is almost an order of magnitude difference, and may need further investigation... Adam ___ 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 )
Re: [Zope-dev] installer branch
At 12:38 AM 8/22/02, Chris McDonough wrote: I have created (yet another, perhaps) easy Zope install branch off the current Zope trunk. It allows for a ./configure; make; make install sort of Zope installation for the source release. It also includes a version of the nascent zctl.py that has been floating around unreleased to make starting, stopping, and debugging Zope easier. I'd like to know if folks are in favor of such a beast. Absolutely in favor. But then again I'm biased, after struggling to get the old way to play nice with RPM :-) Adam ___ 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] 2.6.0a1 CHANGES.txt doc-bug
The change log: http://www.zope.org/Products/Zope/2.6.0a1/CHANGES.txt Contains no mention of Zope 2.5.1 beta 2. Bugfixes that were a part of beta2 are listed under the heading after Zope 2.5.1 Some important changes, eg: Fixed a bug in TM.py that would cause database adapters to hang on errors in the second phase of the two-phase commit. .. made it into 2.5.1 final but you wouldn't know it from looking at the above CHANGES.TXT :-) Adam ___ 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] ExternalEditor 0.3??
Today, I was planning to see if I could create a single zopeedit.py that works on both unix and W32.. Looking in CVS I saw that Casey has been busy, and that this is one of many things that have been done already. I also noticed that you were up kinda late last night Casey?!? :-) Anyway, would now be a good time for a 0.3 snapshot? Anything need done / documented / tested first? Thanks, Adam ___ 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] Zope 2.5.1 RPM built and ready for testing
I have built a Zope 2.5.1 source RPM, it's ready for community tasting and testing ;-) Zope Corp, could you please host it, perhaps at http://www.zope.org/Products/Zope/2.5.1 ? I would like to only make it available in .src.rpm format initially, so that users testers can rpmbuild --rebuild it and test it as is, or rpm -Uvh it, look over the installed spec, scripts etc, make changes (please let me know!) and finally rpmbuild -ba the spec. When any and all changes are in I can build a final .src.rpm, this would also be the time to make binary RPMS available. Eventually, I'd like to put the spec, scripts etc into Zope's CVS, so that rpmbuild -ta Zope.tar.gz could be used to generate rpms directly from tarball, as retrieved by: http://cvs.zope.org/Zope/Zope.tar.gz?tarball=1only_with_tag=Zope-2_5-branch; for example. This part might take a while, I looked at what was done in the spec of courier-imap-1.4.5.tar.gz and it seems to be a fairly involved task... It may be best to wait for InstallationAndConfiguration of Proposals to be implemented for the default build / install of Zope before attempting to dynamically wrap this process with RPM. Questions, comments, suggestions, patches, changes, feedback etc are welcome and encouraged. Adam ___ 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] Final Python 2.1.x and Zope 2.5.x releases?
Fellow bleeding edge Zopers, (Zopesters, Zopeheads, Zopers and Zopists too) Firstly, I'd like to thank everyone who has worked on the Segfault Saga, esp. Matthew and Leonardo! Obviously now that it's fixed, all that's left to do is to make stability a reality for everybody ;-) Does anyone know of a release timeline for a new bugfix release of Python, be it 2.1.2a or 2.1.3? (I am hoping that Zope's need for this will cause it to be sooner rather than later) Are there any outstanding issues with Zope 2.5.1b1 preventing a 2.5.1b2 or 2.5.1-final release? I.E. should we be expecting to see a new Zope release this week? Adam ___ 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 )
Re: [Zope-dev] OpenSSH configuration between ZEO clients storage server
At 12:01 PM 3/27/02, Itamar Shtull-Trauring wrote: Shane Hathaway wrote: But you don't need reliability compensation to multiplex. SSH assumes the transport layer is reliable. So an SSH tunnel and an SSL tunnel are virtually synonymous. They're not really, but yeah, I was wrong :) A SSL forwarder takes a packet, and then sends over another TCP connection that happens to be encrypted. It's basically a TCP port forwarder. Multiple client connections through the local SSL forwarder (e.g. stunnel) will run over *multiple* outgoing streams: client -- stunnel on localhost --- stunnel on www.foo.com server on www.foo.com SSH OTOH uses a multiplexing protocol, where multiple streams of data run over the same connection, and each have their own flow control. Multiple client connections over a SSH port forwarder will run over the same *single* stream. A third thing is TCP over TCP, i.e. PPP over SSH or SSL, which functions as a full network connection. The Python standard library has good support for an SSL client but not for an SSL server. pyOpenSSL is good for both servers and clients. Could be better, but it's easy to start using it, especially for select() based servers (its thread-safety is iffy). Twisted's SSL stuff uses it, and latest version of pyOpenSSL may have asyncore example. Yes. The best solution would be for the ZEO protocol to support auth and crypto natively... The next best solution (while you wait) is to use CIPE ;-) As far as I understand it, even regular TCP port forwarding is TCP over TCP and suffers from the unreliable carrier assumption causing excess (eg retransmit) traffic over a reliable channel. Consider: host --TCP-- local interface --TCP tunnel-- local interface --TCP-- host host --TCP-- virtual loopback interface --TCP-- host In this common port forwarding scenario, the SSH or SSL tunnel creates a virtual single loopback interface that the two hosts use to talk to each other, using TCP. The transport that joins these two physical interfaces to create one virtual loopback interface is also TCP. Therefore it's TCP over TCP How much pain this will cause you in the real world really depends on your bandwidth and packet loss rates. If anyone is aware of any special handling that ssh or stunnel does to prevent or reduce duplicate TCP flow control / adaptive retransmission / congestion control, please let me know. Adam ___ 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 )
Re: [Zope-dev] OpenSSH configuration between ZEO clients storage server
For a look at why TCP over TCP is a bad idea, (e.g. ssh port forwarding) see: http://sites.inka.de/sites/bigred/devel/tcp-tcp.html For a solution, see: http://sites.inka.de/~bigred/devel/cipe.html ;-) Adam ___ 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 )
Re: [Zope-dev] A thought for 2.6 about various leaks and memory problems
Interesting. One complication with that scheme is that ther is no convenient place to put caching. If it goes between Pen and Zope, you need many instances of your cache. If it goes between Pen and the clients, Pen's client-clustering is defeated because it sees only one client. Postgresql takes a similar (multi process) approach to achieving stability as apache. see pg 4 of http://developer.postgresql.org/pdf/transactions.pdf Think shared memory caching behind the Zope worker processes ;-) And web server / proxy shared memory caching in front of the Zope worker processes. Of course, for stability, there is also the possibility of doing a OpenBSD style audit of the entire Zope (and possibly python) code base to make the code as close to perfect (and therefore stable) as the OpenBSD OS is ;-) Volunteers? Adam ___ 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 )
Re: [Zope-dev] Bug days
Europe late afternoon = EST morning How would 1700 UTC (GMT) be for most people? People generally asleep between 12am and 6am. Therefore the best time is logically 2am or so central Pacific time (affecting very few) This is corresponds to 2pm GMT, 9am US EST, etc Adam ___ 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 )
Re: [Zope-dev] Zope 2.6 planning - call for contributors!
FYI, everyone who's following this: I have hijacked http://dev.zope.org/Wikis/DevSite/Proposals/InstallationAndConfiguration for this purpose. :-) Awesome. Exactly how I'd like the default zope install to be structured. :-) Adam ___ 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 )
Re: [Zope-dev] Re: bug in VirtualHostMonster in 2.5.0
I can confirm that throwing this at a Zope 2.5.0 root VirtualHostMonster: http://localhost:8080/VirtualHostBase/http/example.org:80/VirtualHostRoot/_vh_zopeRoot/ provides a page with this link: http://example.org//zopeRoot/p_/ZopeButton and on 2.4.4 you get: http://example.org/zopeRoot/p_/ZopeButton This would suggest that VHM is indeed broken in 2.5.0, or at least the combined result of VHM and HTTPRequest.py URL munging is broken. Adam ___ 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 )
Re: [Zope-dev] Re: bug in VirtualHostMonster in 2.5.0
I tried out version 1.6 of: http://cvs.zope.org/Zope/lib/python/Products/SiteAccess/VirtualHostMonster.py dated 2002/02/15 21:20:33 It works!! I got the correct: http://example.org/zopeRoot/p_/ZopeButton link on the page when I pointed my browser at: http://localhost:8080/VirtualHostBase/http/example.org:80/VirtualHostRoot/_vh_zopeRoot/ I found no new versions of : http://cvs.zope.org/Zope/lib/python/ZPublisher/HTTPRequest.py in CVS added since 2.5.0 release. So it's fixed, but. Which fix??? Leo's, or the one in CVS?? The VirtualHostMonster.py mods are obviously less likely to break other stuff, even if it may be better to fix the bug in HTTPRequest.py By fixing the non-string handling to be consistent with the string handling, the VHM bug disapears Thanks Leo Fri Feb 15 21:19:42 2002 UTC (6 days, 3 hours ago) by evan Fix bugs with _vh_ and empty paths Thanks Evan Gotta love the OSS community What? You mean not only is the bug fixed, but now I have to choose which of the different ways of fixing it I want? Adam ___ 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 )
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 )
Re: [Zope-dev] Zope 2.4.4, when?
At 09:10 AM 1/21/02, Leonardo Rochael Almeida wrote: Guys, please, We really need 2.4.4 and our client won't accept a CVS version. 2.5 betas won't do it either. I think that's the case in many environments, mine included. I've been seriously considering rolling 2.3.3 back out just for the long uptimes (2months) I was getting. In the meantime does anyone have a good monitoring script that can check Zope with wget or something and issue a service zope restart when appropriate? What is holding 2.4.4 back? Is there anything you need help with? testing? bugfix? Yes, what do you need help with? Need someone to thoroughly audit all the changes between 2.4.3 and Zope-2_4-branch for example? I'm going to have to do this, and roll a new .src.rpm for my own use anyway Adam. ___ 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 )
Re: [Zope-dev] Patch acceptance. What about this one?
Just to be safe ... You shouldn't use this entire patch unless your server is behind apache or a proxy server and best if protected by a firewall. It could open a potential security leak if you use the domains field for authentication and the zope server is not protected by apache. Is the issue that the X-Forwarded-For header controls the domain setting? yes ... everyone should probably not use this patch right-out-of-the-box. Thanks guys! My apologies if I kicked the ball a little harder than was needed to get it rolling. In any case, it looks like a little more work is required before this patch will be ready for mainstream. 'HTTP_X_FORWARDED_FOR' should probably be ignored unless Zope is explicitly told to look at it. A list of allowed proxiers, perhaps set as a startup parameter? Or a switch to turn it on (off by default) and a warning about restricting where direct connections to Zope are allowed from? In the meantime, a couple of restrictive firewall rules on the my Zope box will prevent malicious users from connecting directly to Zope with fake HTTP_X_FORWARDED_FOR. Adam ps. Soon as I get it all working perfectly I'll be putting everything I know about using Zope with mod_proxy in a doc for zope.org. (Yes, yet another match when you search for proxypass, hopefully the last needed for while.) ___ 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] Patch acceptance. What about this one?
Fellow Zope addicts, I do both name and IP based virtual hosting from a single Apache instance, proxypassing to various different places within Zope. It works great, with or without Apache working mod_ssl magic! Except. There's a little issue with Zope logging to be solved. Zope logs the IP of the Apache server, not the client. Oops. I might want to track where all administrative logins are really coming from, for example! So I decided to try searching this list before rolling my sleeves up and fixing it myself. Here's what I found: http://www.mail-archive.com/zope-dev@zope.org/msg07600.html Well it appears that Joseph has already solved it for me. Great, gotta love this community. Probably a cleaner patch than what I could have come up with anyway. And I don't have to spend hours digging through the Zope source to get it done! Except... It was written against 2.4.1 I run 2.4.3. It would have been really nice if it had been included in Zope 2.4.next.. Hmm, has anything else changed that I need to be aware of before applying the patch? Lets go to cvs.zope.org and see: First I look at Diff for /Zope/ZServer/medusa/http_server.py between version 1.26.4.2 and 1.30.36.1. Changes. Looks like some careful inspection of the code and some testing is in store for me. And more porting work next time I upgrade Zope... and next time. I can't help but wonder why something this simple and useful was not just included in Zope 2.4.next? It would have saved me and all the poor fools like me so much duplicated effort... Just another Zope Admin's 2 cents worth.. Adam ___ 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 )
