[Zope-dev] Re: Sessions, ConflictError and emails
See the discussion on plone-dev a while ago, link integrity checking will make Plone 3.0 broken and dangerous. Worth trying with 2.9.8 at least. Laurence --On 18. August 2007 21:03:43 +0200 Andreas Jung [EMAIL PROTECTED] wrote: --On 23. Juli 2007 08:53:32 +0200 Wichert Akkerman [EMAIL PROTECTED] wrote: Previously Andreas Jung wrote: Having SecureMailhost as a replacement for MailHost would have been a nice addition to the Zope core..but you choose to go with your own implementation :- If possible I want to try and move Plone 3.5 to zope.sendmail, which seems to be much cleaner than all the MailHost/SecureMailHost/DropMailHost/etc. products combined. There is now TransactionalMailHost (on top of zope.sendmail) http://svn.zope.org/Products.TransactionalMailHost/ providing transaction-aware Mailhost support + support for TLS/SSL (like in SecureMailHost - however it requires yet an unofficial zope.sendmail branch). I think this should make most Mailhost excrescences obsolete. If there is some functionalty missing I would be happy to add it (if it makes sense). In addition the same functionality + asynchronous mail delivery (similar to Maildrophost but without having an external process) will be available as part of the standard Zope MailHost implementation in Zope 2.11. Andreas ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 6 OK
Summary of messages to the zope-tests list. Period Mon Feb 18 12:00:00 2008 UTC to Tue Feb 19 12:00:00 2008 UTC. There were 6 messages: 6 from Zope Unit Tests. Tests passed OK --- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Mon Feb 18 21:03:01 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009137.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Mon Feb 18 21:04:31 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009138.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Mon Feb 18 21:06:02 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009139.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Mon Feb 18 21:07:32 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009140.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Unit Tests Date: Mon Feb 18 21:09:02 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009141.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Mon Feb 18 21:10:32 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009142.html ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope3 server control machinery is untested
This only applies to Zope3 developers and people using the Zope 3 ZMI. I'm trying to get rid of ThreadedAsync. zope.app.server uses it to cause the asyncore main loop to stop as part of the server-control functionality. There are no tests for this afaict. Trying this throigh the web, shutdown seems to work, but not restart. (It looks like restart doesn't work because the exit status os only used to exit the loop. It isn't used in the call to sys.exit.) I propose, at least, to remove this untested functionality from zope.app.server. I'd be for removing it from zope.app.twisted, if it is there, and for removing the UI from zope.app.applicationcontrol. Thoughts? JIm -- Jim Fulton Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope3 server control machinery is untested
On Feb 19, 2008, at 8:59 AM, Lennart Regebro wrote: On Tue, Feb 19, 2008 at 12:43 PM, Jim Fulton [EMAIL PROTECTED] wrote: This only applies to Zope3 developers and people using the Zope 3 ZMI. I'm trying to get rid of ThreadedAsync. zope.app.server uses it to cause the asyncore main loop to stop as part of the server-control functionality. There are no tests for this afaict. Trying this throigh the web, shutdown seems to work, but not restart. (It looks like restart doesn't work because the exit status os only used to exit the loop. It isn't used in the call to sys.exit.) I propose, at least, to remove this untested functionality from zope.app.server. I'd be for removing it from zope.app.twisted, if it is there, and for removing the UI from zope.app.applicationcontrol. Thoughts? Does this mean you remove the possibility to shutdown or restart a Zope3 server from the ZMI? Yes. That is a quite practical thing to be able to do, especially when you don't know with what user the server has been started with so you can't stop or restart it from the command line... It can't be that useful since restart doesn't work and no one bothered to write a test for this functionality. The run-time information tab provides the pid, so shutting down from the command line should be straightforward. Jim -- Jim Fulton Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope3 server control machinery is untested
On Tue, Feb 19, 2008 at 12:43 PM, Jim Fulton [EMAIL PROTECTED] wrote: This only applies to Zope3 developers and people using the Zope 3 ZMI. I'm trying to get rid of ThreadedAsync. zope.app.server uses it to cause the asyncore main loop to stop as part of the server-control functionality. There are no tests for this afaict. Trying this throigh the web, shutdown seems to work, but not restart. (It looks like restart doesn't work because the exit status os only used to exit the loop. It isn't used in the call to sys.exit.) I propose, at least, to remove this untested functionality from zope.app.server. I'd be for removing it from zope.app.twisted, if it is there, and for removing the UI from zope.app.applicationcontrol. Thoughts? Does this mean you remove the possibility to shutdown or restart a Zope3 server from the ZMI? That is a quite practical thing to be able to do, especially when you don't know with what user the server has been started with so you can't stop or restart it from the command line... -- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64 ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope3 server control machinery is untested
Hi, Jim Fulton schrieb: This only applies to Zope3 developers and people using the Zope 3 ZMI. I'm trying to get rid of ThreadedAsync. zope.app.server uses it to cause the asyncore main loop to stop as part of the server-control functionality. There are no tests for this afaict. Trying this throigh the web, shutdown seems to work, but not restart. (It looks like restart doesn't work because the exit status os only used to exit the loop. It isn't used in the call to sys.exit.) I propose, at least, to remove this untested functionality from zope.app.server. I'd be for removing it from zope.app.twisted, if it is there, and for removing the UI from zope.app.applicationcontrol. Thoughts? That code sounds very familiar and reminds me of my first sprint. IIRC we opted out testing this code because we didn't know how to do that. Personally I haven't been using this button at all the console scripts are much more convenient for me. grok currently exposes the functionality in a very accessible way through the standard UI though. Christian -- gocept gmbh co. kg - forsterstrasse 29 - 06112 halle (saale) - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope3 server control machinery is untested
On Tue, Feb 19, 2008 at 3:10 PM, Jim Fulton [EMAIL PROTECTED] wrote: It can't be that useful since restart doesn't work and no one bothered to write a test for this functionality. It's less useful in Zope3 than in Zope2, that's for sure. -- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64 ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] can we teach official Zope to start detecting HTTPS header?
I'm told that, here at Georgia Tech, we are running our Plone's Zope
2.10 behind pound, and that we need some way to signal it about
which requests are coming in through http and which came through
https, so that all of the links generated by Plone can start with
the right protocol. So at the moment, users who type an https URL
so that they can edit documents and enjoy some privacy immediately get
kicked back to the http protocol the first time they click on a
link.
For an earlier version of our site, back on an earlier version of Zope
and Plone, we edited Zope so that it detected an HTTPS header, if
one was present, and allowed the value:
HTTPS: on
to change the protocol variable from HTTP to HTTPS. Then we told
pound to provide that header when an https request was made, and to
delete the header otherwise, and everything worked fine.
Would there be any chance of getting this change into Zope trunk
today, or is it too specific a need to be worth adding to the code
just for us folks using pound at Georgia Tech?
The patch, in the form in which we first wrote it back at the
beginning of 2007, is attached for the curious. Thanks for any feedback!
--- /usr/local/zope-2.9.5/lib/python/ZPublisher/HTTPRequest.py 2006-10-02 11:53:33.0 -0400
+++ /usr/local/zope-2.9.5/lib/python/ZPublisher/HTTPRequest.py 2007-01-03 18:20:35.0 -0500
@@ -294,6 +294,10 @@
if have_env('HTTPS') and (
environ['HTTPS'] == on or environ['HTTPS'] == ON):
protocol = 'https'
+elif have_env('HTTP_HTTPS') and (
+environ['HTTP_HTTPS'] == on or
+environ['HTTP_HTTPS'] == ON):
+protocol = 'https'
elif (have_env('SERVER_PORT_SECURE') and
environ['SERVER_PORT_SECURE'] == 1):
protocol = 'https'
--
Brandon Craig Rhodes [EMAIL PROTECTED] http://rhodesmill.org/brandon
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Mail to checkins list not coming through
Hi, I have Zope commit rights now. I have subscribed to the zope-checkins list: http://mail.zope.org/mailman/options/zope-checkins But when I commit something (I committed to the Sandbox and today to z3c.sqlalchemy) I get an email: = Your mail to 'Checkins' with the subject SVN: Sandbox/mauritsvanrees-svn-test/ Removing test for my svn write access. Is being held until the list moderator can review it for approval. The reason it is being held: Post by non-member to a members-only list = I am definitely a member though: I got a confirmation message about that and can edit my options. But I do not get any email and I am not allowed to post, so that suggests otherwise. Maybe a mailing list admin can look at outstanding moderator requests? Thanks, -- Maurits van Rees | http://maurits.vanrees.org/ Work | http://zestsoftware.nl/ This is your day, don't let them take it away. [Barlow Girl] ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Mail to checkins list not coming through
Jim Fulton, on 2008-02-19: You were getting this from the Checkins list, not zope-checkins. I've updated the list to accept your posts. Ah, I see. They come through now. Thanks. -- Maurits van Rees | http://maurits.vanrees.org/ Work | http://zestsoftware.nl/ This is your day, don't let them take it away. [Barlow Girl] ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Mail to checkins list not coming through
You were getting this from the Checkins list, not zope-checkins. I've updated the list to accept your posts. Jim On Feb 19, 2008, at 4:01 PM, Maurits van Rees wrote: Hi, I have Zope commit rights now. I have subscribed to the zope-checkins list: http://mail.zope.org/mailman/options/zope-checkins But when I commit something (I committed to the Sandbox and today to z3c.sqlalchemy) I get an email: = Your mail to 'Checkins' with the subject SVN: Sandbox/mauritsvanrees-svn-test/ Removing test for my svn write access. Is being held until the list moderator can review it for approval. The reason it is being held: Post by non-member to a members-only list = I am definitely a member though: I got a confirmation message about that and can edit my options. But I do not get any email and I am not allowed to post, so that suggests otherwise. Maybe a mailing list admin can look at outstanding moderator requests? Thanks, -- Maurits van Rees | http://maurits.vanrees.org/ Work | http://zestsoftware.nl/ This is your day, don't let them take it away. [Barlow Girl] ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope ) -- Jim Fulton Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] can we teach official Zope to start detecting HTTPS header?
The reason that that more folks probably don't complain about this is that they probably use Apache to do URL rewriting in conjunction with Zope's virtual host monster. And under that scenario, you indicate that you want Zope to generate https urls within the Apache rewrite rule as opposed to within a separate header. That said, it'd be fine to put this in, it would cause absolutely no harm. (Although I'm not volunteering, every time I try to check something in to the Zope repository these days, Philipp yells at me about style, so I'm getting gun-shy... ;-) ) - C Brandon Craig Rhodes wrote: I'm told that, here at Georgia Tech, we are running our Plone's Zope 2.10 behind pound, and that we need some way to signal it about which requests are coming in through http and which came through https, so that all of the links generated by Plone can start with the right protocol. So at the moment, users who type an https URL so that they can edit documents and enjoy some privacy immediately get kicked back to the http protocol the first time they click on a link. For an earlier version of our site, back on an earlier version of Zope and Plone, we edited Zope so that it detected an HTTPS header, if one was present, and allowed the value: HTTPS: on to change the protocol variable from HTTP to HTTPS. Then we told pound to provide that header when an https request was made, and to delete the header otherwise, and everything worked fine. Would there be any chance of getting this change into Zope trunk today, or is it too specific a need to be worth adding to the code just for us folks using pound at Georgia Tech? The patch, in the form in which we first wrote it back at the beginning of 2007, is attached for the curious. Thanks for any feedback! ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
AW: [Zope-dev] can we teach official Zope to start detecting HTTPSheader?
Hi Chris Betreff: Re: [Zope-dev] can we teach official Zope to start detecting HTTPSheader? [...] (Although I'm not volunteering, every time I try to check something in to the Zope repository these days, Philipp yells at me about style, so I'm getting gun-shy... ;-) ) Philipp? Who's that ;-) I think another problem is that we do not understand what zope is or should be in the near future. Or at least not everybody drives in the same direction. This makes it very hard for optimization and do the right thing in the right place. We really need to clarify the direction of zope and it's zope.* packages in the near future. Then this whould allow us to do the optimization which is the next big step which I think is really needed. Regards Roger Ineichen - C ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
