From: Steve V. <vi...@ie...> - 2008-10-20 16:04:59
|
On 10/20/08, Dominique Boucher <dom...@nu...> wrote: > > When downloading a large (static) document from a Yaws-powered web site with > IE, the download progress bar is not displayed when the file is opened > instead of just saved. This is quite annoying. The problem seems to be that > the "Content-Disposition" header is missing from the HTTP response (I made a > quick and dirty hack to yaws_server.erl to confirm this). > > > > What would be the preferred way to add this header automatically (other than > patch Yaws itself)? That depends on what's serving the file. If you're delivering the response out of any out/1 function, you can set any header you want by including this in your response: {header, {"Header_name", "Header_value"}} of course replacing Header_name and Header_value with appropriate actual string values. I've been making some header-related changes in Yaws svn lately, so I'll take a look at this header and talk it over with Klacke to see if and how we might add support for it. --steve |
From: Dominique B. <dom...@nu...> - 2008-10-20 16:27:06
|
> > What would be the preferred way to add this header automatically > (other than > > patch Yaws itself)? > > That depends on what's serving the file. If you're delivering the > response out of any out/1 function, you can set any header you want by > including this in your response: > > {header, {"Header_name", "Header_value"}} > > of course replacing Header_name and Header_value with appropriate > actual string values. I'm not serving the file myself, I let Yaws do that for me. That's why I thought this should be done automatically by Yaws. > I've been making some header-related changes in Yaws svn lately, so > I'll take a look at this header and talk it over with Klacke to see if > and how we might add support for it. Great, thanks. Dominique |
From: Claes W. <kl...@ta...> - 2008-10-20 19:42:29
|
Dominique Boucher wrote: >>> What would be the preferred way to add this header automatically >> (other than >>> patch Yaws itself)? Patching yaws does seem to be the right answer, so for all file types that are not rendered by the browser it seems to make sense to just set this header. I didn't even know it existed prior to this. Do all browsers play well with this ? Do you know ? It's easy to add. Again, instead of just checking for myself, I'm asking if you know. What do other http servers e.g. apache do here ? /klacke |
From: Dominique B. <dom...@nu...> - 2008-10-20 20:22:35
|
> Dominique Boucher wrote: > >>> What would be the preferred way to add this header automatically > >> (other than > >>> patch Yaws itself)? > > Patching yaws does seem to be the right answer, so for all file > types that are not rendered by the browser it seems to make sense > to just set this header. > > I didn't even know it existed prior to this. Do all browsers play > well with this ? Do you know ? The browsers I usually use do not complain (Firefox, Google Chrome). But the header is only a hint to the browser. It may ignore it. (That's my understanding.) > It's easy to add. Again, instead of just checking for myself, I'm > asking > if you know. What do other http servers e.g. apache do here ? I think you have to manually tell the http server to add the header. This is not done by default. With Apache, you use the <Files> or <FilesMatch> directives to do that (that's what I read while googling around). Dominique |