Re: Content-Length header should be set usingap_set_content_length
"Rob Saccoccio" <[email protected]>
| Newsgroups | gmane.comp.web.fastcgi.devel |
|---|---|
| Message-ID | <ACAF580D7BBC488A8842D87A2A5BB64D@maisel> |
Committed. Thanks. Rob > -----Original Message----- > From: fastcgi-developers-bounces+robs=fastcgi.com-xGejAJT2w6xVgU18Zptdi0EOCMrvLtNR@public.gmane.org > [mailto:fastcgi-developers-bounces+robs=fastcgi.com-xGejAJT2w6xVgU18Zptdi0EOCMrvLtNR@public.gmane.org] > On Behalf Of Artur Zaprzala > Sent: Tuesday, November 04, 2008 10:17 AM > To: fastcgi-developers-xGejAJT2w6xVgU18Zptdi0EOCMrvLtNR@public.gmane.org > Subject: [FASTCGI] Content-Length header should be set > usingap_set_content_length > > Content-Length header should be set using ap_set_content_length() function > in > process_headers(). I fixed this about 3 years ago and I don't remember > what was > the problem with the current aproach, but it surely was. > > Today I did some research to support my fix. > > Currently process_headers() adds Content-Length to err_headers_out. Here > is > description of err_headers_out from Apache documentation: > > The difference between headers_out and err_headers_out is that the > latter are printed even on error, and persist across internal redirects > (so the headers printed for ErrorDocument handlers will have them). > > And Content-Length shouldn't persist across internal redirects.