DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24884>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24884 When the response is 304 Apache doesn't include cache headers ------- Additional Comments From [EMAIL PROTECTED] 2003-12-02 00:02 ------- The solution lies somewhere within the following: mod_expires only register with "ap_register_output_filter"... and within "modules/http/http_protocol.c", we do this (flushing the output filter): AP_DECLARE(void) ap_send_error_response(request_rec *r, int recursive_error) { int status = r->status; int idx = ap_index_of_response(status); char *custom_response; const char *location = apr_table_get(r->headers_out, "Location"); /* At this point, we are starting the response over, so we have to reset * this value. */ r->eos_sent = 0; /* and we need to get rid of any RESOURCE filters that might be lurking * around, thinking they are in the middle of the original request */ r->output_filters = r->proto_output_filters; --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
