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.
