I've been having troubles with IE downloads too, in my case it was with a 
simple bibtex.bib file (format for bibliographic data). Error message was 
always about the file not existing. I'm not using https, but I am running 
behind a proxy/load-balancer. Had me tearing out my hair for a while. Worked 
out of the bow on FF and Safari, but not in IE. In the end I got it working by 
adding the following to my output type:
<parameter name="Content-Disposition">filename="bibtex.bib"</parameter>
<parameter name="Pragma">public</parameter>
<parameter name="Cache-Control">max-age=0</parameter>

Haven't tested in in IE7. Hope it doesn't blow up there. No idea if it could 
help you, but someone else might benefit from it one day.

Greetings,
Koen

> -----Oorspronkelijk bericht-----
> Van: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] Namens Veikko Mäkinen
> Verzonden: donderdag 23 augustus 2007 12:27
> Aan: Agavi Users Mailing List
> Onderwerp: [Agavi-Users] Modifying session_cache_limiter 
> based on output typeand HTTP_USER_AGENT
> 
> Hi everyone,
> 
> I'm having troubles with IE, HTTPS and PDF ouput type and 
> according to a blog article
> (http://joseph.randomnetworks.com/archives/2004/10/01/making-i
> e-accept-file-downloads)
> Google found for me I need to do
> 
> if(strpos($_SERVER['HTTP_USER_AGENT'], 'MSIE')) {
>    session_cache_limiter('public');
> }
> 
> but before "session_start()" (executed in 
> AgaviSessionStorage::startup())
> 
> 
> Doing this for every request doesn't seem good so I wanted to 
> do for the PDF output type only. But SessionStorage doesn't 
> know the output type when it starts the session.
> 
> I can't figure out anything but nasty hacks to get this to 
> work... any ideas are greatly appreciated.
> 
> 
> -veikko
> 
> 
> _______________________________________________
> users mailing list
> [email protected]
> http://lists.agavi.org/mailman/listinfo/users
> 

_______________________________________________
users mailing list
[email protected]
http://lists.agavi.org/mailman/listinfo/users

Reply via email to