On Thu, Jan 30, 2003 at 02:36:53PM +0000, Matt Sergeant wrote: > > And I don't really think it's designed to output a header. Tables where > > used because it made it easy to implement (I assume), and it's only in > > mod_perl and not the C api that there are specific functions for adding > > to r->headers_out and r->err_headers_out, so ultimatively if anything > > should deal with it, it's either the mod_perl functions OR as Matt has > > submitted around line 1570 (in my non-up-to-date cvs copy) in > > http_protocol.c, and yes, I do believe it's the right thing to do so you > > can't output \n nor \r's in headers. > > I'm not really sure it's possible to fix in mod_perl either. Otherwise I > would have done it there because I find it easier to maintain a patched > mod_perl than a patched Apache.
What I was thinking was just that since you can add a header with $r->headers_out->add it would be possible to add something there to remove newlines, but since it's probably just an Apache::Table operation it wouldn't "know" which table it is working on either. Actually getting it fixed in Apache will probably benefit many other people and not just modperl users (not probably, it will!) Are they being responsive or? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
