(bug/Zope 1.11.0pr1) Content-Type header from a DTML Method/Document are ignored
Hello, Zope 1.11.0 seems to ignore Content-Type headers Let 'dm' be this DTML Method: <!--#var "RESPONSE.setHeader('Content-Type', 'application/rtf')"-->{\rtf1\ansi ....} Of course, .... is the rest of the rtf document. Note that it is dynamicly generated. This is why I need to use a DTML Method to render the RTF document. Under Zope 1.10.2, dm renders nicely (Word is launched and the RTF document is seen directly in the browser from IE 3.x. From Navigator 4.5, I can either save or open the document). However, under Zope 1.11.0pr1, IE 3.x says it can't open the document. At the end of the document is what ZServer displays. However, there is no error with Navigator, but it displays the RTF file as text. A freshly-installed-from-source-Zope 1.11.0pr1 exhibits the same behavior. What ZServer prints: uncaptured python exception, closing channel <zhttp_channel connected 160.0.108.48:1944 at 84d15b8 channel#: 84 requests:1> (socket.error:(9, 'Mauvais descripteur de fichier.') [/home/webdevel/devel/11.0/Zope/ZServer/medusa/asynchat.py|initiate_send|204 ] [/home/webdevel/devel/11.0/Zope/ZServer/medusa/http_server.py|send|386] [/home/webdevel/devel/11.0/Zope/ZServer/medusa/asyncore.py|send|233] ) Can someone post this to the Collector for me? Regards, Jephte CLAIN Service Informatique CHSR
participants (1)
-
Service Informatique CHSR