Hi again,

Now I would like to serve some PDF-Content with Zope/External
Method.

Any Browser but ... IE ... can do this job ;-)

Some of the header seem to be rewriten inbetween,
a normal unencrypted connection or a ssl-tunnel
deliver the same PDF-Content just as intentend.


Please comment,
Sascha


-- 
Forget Aging and Die Forever!

The file must be named xxxx.pdf -- and you should provide the usual 
mime headers for standards complient browsers.  Differen IE versions 
behave differently, or so I am lead to believe.


On Tue, 16 Dec 2003, Sascha Gresk wrote:

> Hi again,
> 
> Now I would like to serve some PDF-Content with Zope/External
> Method.
> 
> Any Browser but ... IE ... can do this job ;-)
> 
> Some of the header seem to be rewriten inbetween,
> a normal unencrypted connection or a ssl-tunnel
> deliver the same PDF-Content just as intentend.
> 
> 
> Please comment,
> Sascha
> 
> 
> -- 
> Forget Aging and Die Forever!
> 

Am 16.12.2003 um 00:44 schrieb Dennis Allison:

> The file must be named xxxx.pdf

Okay I have done that, but it does not seem to
be required.

> -- and you should provide the usual 
> mime headers for standards complient browsers.

I did that, but something seems to get modified by pound.

> Differen IE versions
> behave differently, or so I am lead to believe.

No Pound - no Problem - but no encryption.

Here are some of my headers I am using:

     RESPONSE.setHeader("Content-Length",len(pdf))
     RESPONSE.setHeader('Content-Type', 'application/pdf')
     RESPONSE.setHeader('Content-disposition','inline; 
filename="%s.pdf"' % ("druck"))

These Header *work* in an unencrypted connection.


regards,
Sascha


-- 
Forget Aging and Die Forever!

>
> Am 16.12.2003 um 00:44 schrieb Dennis Allison:
>
>> The file must be named xxxx.pdf
>
> Okay I have done that, but it does not seem to
> be required.
>
>> -- and you should provide the usual
>> mime headers for standards complient browsers.
>
> I did that, but something seems to get modified by pound.
>
>> Differen IE versions
>> behave differently, or so I am lead to believe.
>
> No Pound - no Problem - but no encryption.
>
> Here are some of my headers I am using:
>
>      RESPONSE.setHeader("Content-Length",len(pdf))
>      RESPONSE.setHeader('Content-Type', 'application/pdf')
>      RESPONSE.setHeader('Content-disposition','inline;
> filename="%s.pdf"' % ("druck"))
>
> These Header *work* in an unencrypted connection.


IIRC Pound has nothing to do with it. IE behaves different when using http
or https. I had the same problem with downloading CSV files from a
Squirrelmail plugin.

Simon

>
>
> regards,
> Sascha
>
>
> --
> Forget Aging and Die Forever!
>
>

On Tuesday 16 December 2003 09:24, Sascha Gresk wrote:
> Am 16.12.2003 um 00:44 schrieb Dennis Allison:
> > The file must be named xxxx.pdf
>
> Okay I have done that, but it does not seem to
> be required.
>
> > -- and you should provide the usual
> > mime headers for standards complient browsers.
>
> I did that, but something seems to get modified by pound.
>
> > Differen IE versions
> > behave differently, or so I am lead to believe.
>
> No Pound - no Problem - but no encryption.
>
> Here are some of my headers I am using:
>
>      RESPONSE.setHeader("Content-Length",len(pdf))
>      RESPONSE.setHeader('Content-Type', 'application/pdf')
>      RESPONSE.setHeader('Content-disposition','inline;
> filename="%s.pdf"' % ("druck"))
>
> These Header *work* in an unencrypted connection.

I assure you Pound does NOT modify these headers (look at the source to 
convince yourself).

I suggest you try an SSL connection via stunnel to verify that indeed this is 
an issue of IE/HTTPS rather than Pound.
-- 
Robert Segall
Apsis GmbH
Postfach, Uetikon am See, CH-8707
Tel: +41-1-920 4904