Hello,
Finally, I found one solution. You only have to add expires parameter for the map:read as follow :

<map:read src="" mime-type="application/msword">
       <map:parameter name="expires" value="100"/>
</map:read>

This seems to force IE to bypass the error obtained on the first call to the document.
This is not the better solution but it's working, without to write a specific servlet or modify actual reader component as mentionned in previous suggestions.
Nevertheless, I obtain twice the following WARN message when accessing PDF documents (not with DOC) but hte document is correctly accessed :
==========
        WARN!! Invalid length: Content-Length=98945 written=3138 for http://localhost:8888/test.pdf
        WARN!! Invalid length: Content-Length=98945 written=3138 for http://localhost:8888/test.pdf
============

One other interesting and recent relative link I found on the subject is :
http://archives.real-time.com/pipermail/cocoon-users/2004-February/046611.html

This initial problem should be keept in a todo list.
Regards.


Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
list-help: <mailto:[EMAIL PROTECTED]>
list-unsubscribe: <mailto:[EMAIL PROTECTED]>
list-post: <mailto:[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Delivered-To: mailing list [EMAIL PROTECTED]
Subject: RE: ressource reader bug with IE (linked to caching)
Date: Tue, 20 Apr 2004 16:08:22 +0200
Thread-Topic: ressource reader bug with IE (linked to caching)
Thread-Index: AcQmx4QjKjOUIwcMQsayGi5C8Qfj2wAGMvYA
From: "Carmona Perez, David" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
X-OriginalArrivalTime: 20 Apr 2004 14:08:22.0768 (UTC) FILETIME=[F0CC7F00:01C426E0]
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

I detected the same problem and posted to Bugzilla, with a patch, taken from Cocoon 2.0.4 which didn't have this bug.
 
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24647
 
Hope this helps.

 -----Mensaje original-----
De: Joel Reungoat [mailto:[EMAIL PROTECTED]]
Enviado el: martes, 20 de abril de 2004 13:05
Para: [EMAIL PROTECTED]
Asunto: ressource reader bug with IE (linked to caching)

Hello users,

I'm trying to access DOC or PDF files using the ressource reader component as described in the sitemap below and get the following error only under Microsoft IE :

>>>>>>>>>>

Internet Explorer cannot download test.doc from localhost

Internet Explorer was not able to open this Internet site. The
requested
site is either unavailable or cannot be found. Please try again later.
>>>>>>>>>>
This message also only appears at the first attempt. It seems that at first attempt, the file has been prepared in the cache. So, if  I refresh the page a second time from IE, I get and open correctly my document under Word (or Acrobat if pdf).

When using Mozilla navigator, there is no problem at first attempt.
Also, if a first attempt is made from Mozilla, then the first attempt from IE is working.
So it seems that Cocoon caching is implicated.
I made a test in the sitemap by forcing "noncaching" for the pipeline. And then, I can not access at all to my document.

Does anybody have a solution for this problem ?

My cocoon version : 2.1.4
My IE version : 5.5 (probably problems also with 6.0)
IE configaration for caching page : "automatic" (other choice produces same problem)
Other links I found without answers : http://www.mail-archive.com/[EMAIL PROTECTED]/msg07949.html
http://www.mail-archive.com/[EMAIL PROTECTED]/msg04959.html

Here is my sitemap :
<?xml version="1.0" encoding="UTF-8"?>
<map:sitemap xmlns:map="http://apache.org/cocoon/sitemap/1.0">
<map:pipelines>
  <map:pipeline type="caching">         <!--   With caching, the problem occurs only at the first read -->
<!-- <map:pipeline type="noncaching">   Without caching, the problem occurs at each attempt -->
        <map:match pattern="**.doc">
        <map:read src="" mime-type="application/msword"/>
      </map:match>
      <map:match pattern="**.pdf">
        <map:read src="" mime-type="application/pdf"/>
      </map:match>
  </map:pipeline>
</map:pipelines>
</map:sitemap>

*************************************************************

Este correo ha sido procesado por el Antivirus del Grupo FCC.
*************************************************************

*************************************************************
Este correo ha sido procesado por el Antivirus del Grupo FCC.
*************************************************************

Reply via email to