Skip to main content

Zope[2] patch to alleviate the effect of https://bugs.launchpad.net/zope2/+bug/740831.

Project description

This package patches the web application server Zope to work around https://bugs.launchpad.net/zope2/+bug/740831.

The bug causes Zope to deliver wrong responses after a request using Response.write has suffered a ConflictError. The patch prevents Zope from retrying such requests and logs an error message when it tries. The bug effect is thus limited to a single request.

Note that even with this patch Zope does not behave fully correctly: in case of a ConflictError, it may deliver a (maybe partial) response even though the transaction has been aborted. The client does not get feedback for the transaction rollback. The only indication is the log record written.

Response.write is inherently unsafe in the face of ConflictError. The only reliable fix is not to use it at all.

The (monkey) patch gets installed when this package is imported.

Project details


Release history Release notifications | RSS feed

This version

1.0

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

File details

Details for the file dm.zopepatches.fix_responsewrite_conflict-1.0.tar.gz.

File metadata

File hashes

Hashes for dm.zopepatches.fix_responsewrite_conflict-1.0.tar.gz
Algorithm Hash digest
SHA256 089772d070e4a413201b433f061bfd5097185ae66133ff76f720354db4601a17
MD5 4eea4c8d67063140fe0181082b54feec
BLAKE2b-256 86cb0a397e44ccc370e6727ab16178ff0d92f274f3906795c2ca1a583b13c9fd

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page