-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jonas Meurer wrote: > Hello, > > When do you plan to add the fix for "request must be post" at "Take > Ownership" to a stable zope 2.10 release? It seems like this bug has > been introduced with zope 2.10.2 or 2.10.3. > > An example of the bug can be found at http://zope.pastey.net/56726 > > It seems like you already submitted a fix to the svn trunk, see > http://mail.zope.org/pipermail/zope-checkins/2007-March/032104.html > > But unfortunately this didn't went into a stable release yet. > > So my question is, do you plan to add this fix to the next zope2.10 > stable release?
The pastebin output above doesn't explain why you think Zope's behavior is a bug: it shows an attempt to call 'manage_takeOwnership' using a non-POST method, which is no longer allowed after the 'postonly' changes. Those changes landed for Zope 2.10.3: http://svn.zope.org/Zope/tags/2.10.3/lib/python/AccessControl/Owned.py Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGjQzN+gerLs4ltQ4RAuUMAKCtaeYH8wGlnEZldVqjy0SJBK5vFQCgwL8L tWsNSDUQuKqNF70Fm5Pk/j4= =9xm8 -----END PGP SIGNATURE----- _______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )