On Sun, 9 Mar 2003, Stas Bekman wrote: > I wish Doug would follow up and explain why was it dumped from the 2.0 API in > first place.
you'll need to ask [EMAIL PROTECTED] for details, but the jist is that filters handle sending headers at the proper time. not sure if the reason matters much, the function was removed from the 2.0 server api, so naturally it removed from the modperl 2.0 api. > We also still have $r->send_cgi_header, which Doug suggested to rename > $r->cgi_header_parse. You can see it here: cosmetic. the method does not send anything, just parses and inserts into headers_out. > I think we need to have: > > $r->skip_cgi_header_parser() which will only turn the parsing flag off. And > porters will replace: > > $r->send_http_header; > > with > > $r->skip_cgi_header_parser; i'm pretty far out of the loop at the moment, but this doesn't sound right. there should be a way to check internally if headers have already been sent. for example, if Content-Type exists in r->headers_out. since nothing but the server should be inserting that header into the table. and such a check should only happen if +ParseHeaders is enabled of course. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
