Bug 48316 - ap_run_insert_filter doesn't work in cache_url_handler
Summary: ap_run_insert_filter doesn't work in cache_url_handler
Status: RESOLVED LATER
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_cache (show other bugs)
Version: 2.2.13
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: MassUpdate
Depends on:
Blocks:
 
Reported: 2009-12-01 03:14 UTC by Dodou Wang
Modified: 2018-11-07 21:07 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dodou Wang 2009-12-01 03:14:22 UTC
when a cache is hit in the quick_handler, the cache_url_handler will execute ap_run_insert_filter to hook all the filter to the request. as the line 207 in mod_cache.c (2.2.13)
-----------------------------------
      /* We are in the quick handler hook, which means that no output
       * filters have been set. So lets run the insert_filter hook.
       */
      ap_run_insert_filter(r);
-------------------------------------

but it didn't work, when the core_insert_filter is invoked by ap_run_insert_filter, the core_dir_config's output_filters is stil NULL, so no filter is hooked to the request. 

I found that the core_dir_config->output_filters doesn't stop to be NULL until the ap_location_walk. so the ap_run_insert_filter in ap_invoke_handler works all right, but in quick_handler it doesn't.
Comment 1 William A. Rowe Jr. 2009-12-01 04:04:40 UTC
By definition, quick_handler is not to be adding extra content filters, once
we find the cache entry, the protocol filters transmit it to the client.

Can you explain what you are trying to do?  Perhaps this is better closed
and discussion moved to modules-dev@ or dev@ httpd (whichever is a more
appropriate list your comments).
Comment 2 William A. Rowe Jr. 2018-11-07 21:07:57 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.