You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Ulrich Mayring <ul...@denic.de> on 2001/04/25 16:45:50 UTC
Internet Explorer/PDF problem resurfaced
Hello,
the Internet Explorer with the newest security patch (version
5.50.4522.1800) again does not load PDFs generated by Cocoon (and ending
in .xml). Apparently in this patch a security hole was fixed that has to
do with MIME types. It was possible to send an unknown MIME type (say
foo/bar) and in reality there was a .exe file inside, which was then
executed.
It looks to me as if the patch effects, that MIME type and file suffix
are compared and if they don't match, an error message is displayed.
Either that or they reverted to the old behavior, where file type is
looked at before MIME type.
Known Workaround: none :-(
Ulrich
--
Ulrich Mayring
DENIC eG, Systementwicklung
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: Internet Explorer/PDF problem resurfaced
Posted by Ulrich Mayring <ul...@denic.de>.
Gritsenko wrote:
>
> There is a workaround, known to me, not known to Ulrich yet ;)
Your workaround doesn't work, though :)
Note the exact version number I provided.
Ulrich
--
Ulrich Mayring
DENIC eG, Systementwicklung
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: Internet Explorer/PDF problem resurfaced
Posted by Elmar Christen <el...@elmartec.de>.
I think you're cool! ;-)
Hm, I was wondering why I could not see my PDFs after installing that
path - now I know why. The workaround - in my case - is not allowed by
requieremens given by my client - too bad.
What about MS-IE6? Does anybody if that thing will cause the same problem?
Gritsenko wrote:
> There is a workaround, known to me, not known to Ulrich yet ;)
> I wouldn't be sarcastic, but I'm trying to be a cool guy, like Ulrich.
>
>
> Somehow start Acrobat (ie find and open *.pdf on Internet using Google, this
> *.pdf should not be Cocoon-originated)
>
> Once you get to Acrobat toolbar, find action Properties or Options in its
> menu (I believe it's ctrl-K also)
>
>
> Once you have Options menu open, find something that tells to integrate or
> not Acrobat from browser,
>
> uncheck it.
>
>
> Result:
>
> If you open Cocoon-originated PDF in MS IExplorer, Explorer will activate
> Acrobat ot see it, but Acrobat will open is separate window, not embedded in
> browser window.
>
>
>
>
>
>
>
> ----- Original Message -----
> From: "Ulrich Mayring" <ul...@denic.de>
> To: <co...@xml.apache.org>
> Sent: Wednesday, April 25, 2001 10:45 AM
> Subject: Internet Explorer/PDF problem resurfaced
>
>
>> Hello,
>>
>> the Internet Explorer with the newest security patch (version
>> 5.50.4522.1800) again does not load PDFs generated by Cocoon (and ending
>> in .xml). Apparently in this patch a security hole was fixed that has to
>> do with MIME types. It was possible to send an unknown MIME type (say
>> foo/bar) and in reality there was a .exe file inside, which was then
>> executed.
>>
>> It looks to me as if the patch effects, that MIME type and file suffix
>> are compared and if they don't match, an error message is displayed.
>> Either that or they reverted to the old behavior, where file type is
>> looked at before MIME type.
>>
>> Known Workaround: none :-(
>>
>> Ulrich
>>
>> --
>> Ulrich Mayring
>> DENIC eG, Systementwicklung
>>
>> ---------------------------------------------------------------------
>> Please check that your question has not already been answered in the
>> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
>>
>> To unsubscribe, e-mail: <co...@xml.apache.org>
>> For additional commands, e-mail: <co...@xml.apache.org>
>>
>
>
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
>
> To unsubscribe, e-mail: <co...@xml.apache.org>
> For additional commands, e-mail: <co...@xml.apache.org>
>
>
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: Internet Explorer/PDF problem resurfaced
Posted by Gritsenko <gr...@home.com>.
There is a workaround, known to me, not known to Ulrich yet ;)
I wouldn't be sarcastic, but I'm trying to be a cool guy, like Ulrich.
Somehow start Acrobat (ie find and open *.pdf on Internet using Google, this
*.pdf should not be Cocoon-originated)
Once you get to Acrobat toolbar, find action Properties or Options in its
menu (I believe it's ctrl-K also)
Once you have Options menu open, find something that tells to integrate or
not Acrobat from browser,
uncheck it.
Result:
If you open Cocoon-originated PDF in MS IExplorer, Explorer will activate
Acrobat ot see it, but Acrobat will open is separate window, not embedded in
browser window.
----- Original Message -----
From: "Ulrich Mayring" <ul...@denic.de>
To: <co...@xml.apache.org>
Sent: Wednesday, April 25, 2001 10:45 AM
Subject: Internet Explorer/PDF problem resurfaced
> Hello,
>
> the Internet Explorer with the newest security patch (version
> 5.50.4522.1800) again does not load PDFs generated by Cocoon (and ending
> in .xml). Apparently in this patch a security hole was fixed that has to
> do with MIME types. It was possible to send an unknown MIME type (say
> foo/bar) and in reality there was a .exe file inside, which was then
> executed.
>
> It looks to me as if the patch effects, that MIME type and file suffix
> are compared and if they don't match, an error message is displayed.
> Either that or they reverted to the old behavior, where file type is
> looked at before MIME type.
>
> Known Workaround: none :-(
>
> Ulrich
>
> --
> Ulrich Mayring
> DENIC eG, Systementwicklung
>
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
>
> To unsubscribe, e-mail: <co...@xml.apache.org>
> For additional commands, e-mail: <co...@xml.apache.org>
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>