On Mon, May 3, 2010 at 11:19 AM, Martin Stjernholm <[email protected]> wrote: > Michael Stenitzer <[email protected]> wrote: > >> works as intended so far, as long as i do not encounter a 404. then my >> 404-page will be sent with the content-disposition header as well. >> naturally this is not what i'm intending. and i can't find a way to >> unset the header. i tried it with the <header /> element but that >> seems to be ignored and not make it to the client. > > <header> can only add headers, not remove them. That could be changed, > but if I were in your shoes I think I'd prefer to set the header only > when I actually want it set, so I won't miss places where it needs to be > unset again. You can do that if you let your module act as a filter > module too. >
i've used the first try module because i'm rewriting the path (like an internal redirect): /forcedownload/somepath -> /somepath so can a module combine a first try with an last try (filter)? i could then set the header only if my rewrite-flag is set and the return-code is 200. /michael
