Ausum Studio wrote:

use_HTTP_content_compression = 1

From some posts in the archives, you'll find that this isn't the right way to enable HTTP content compression...

expect the problem that every time you click at the icon to launch the editor, Windows will start to ask for what to do with the to-download file. If you respond to open, then it will trigger the File Types dialog box, asking for the right app to open it. In other words, you'll be tempted to reinstall ExternalEditor. :)

...but this sounds like a bug similar to one people have experienced in other circumstances with http content compression. IIRC, the person who implemented this is lurking on the list, so hopefully will get back to you... cheers Chris

Nope... the right way is to throw <dtml-call "RESPONSE.enableHTTPCompression(REQUEST)"> in your standard_html_header It works... see...? http://leknor.com/code/gziped.php?url=http%3A%2F%2Fwww.queenswest.com Tried it in a ton of browsers for both Mac and Windows. Seems to work fine. BZ On Saturday, August 2, 2003, at 11:09 PM, Ausum Studio wrote:

I just stumbled with a problem while working with both Zope's gzip compression and ExternalEditor: If you enable gzip in HTTPResponse.py, like this:

use_HTTP_content_compression = 1

expect the problem that every time you click at the icon to launch the editor, Windows will start to ask for what to do with the to-download file. If you respond to open, then it will trigger the File Types dialog box, asking for the right app to open it. In other words, you'll be tempted to reinstall ExternalEditor. :)

Any ideas of how to patch this?

Thanks in advance,

Ausum

_______________________________________________ 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 )