> > Oh, I see what you're saying. What's happening is that if I decline, > it's getting *default*, rather than "what was previously configured". > Is that what you're saying?
yup. > Any way to push another content handler > on the stack, rather than replacing what's there? (Yeah, I can > replace what's there with a list, I know how to do that.) you can stack PerlHandlers, but once you DECLINE past all the ones mod_perl knows about, no, there is no way to escape default-handler at that point. > > > and I can't find any documentation anywhere > > > referring to it; google > > > > use the source, luke. > > After buying a whole book on the topic, in addition to what's online? > Sheesh. I guess if it's the only way, I'll have to. well, we authors try our best to document as much as we can. personally, I had never tried to suppress an ETag header until after ours came out... good thing there are mailing lists where the people who wrote the code and books like to answer questions :) --Geoff -- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
