https://issues.apache.org/bugzilla/show_bug.cgi?id=54706
--- Comment #3 from Yann Ylavic <ylavic....@gmail.com> --- Sorry for my late answer. The patch works well exept in one case: mod_proxy has a stale entry which is not "fresh" (according to. cache_check_freshness), and the origin responds to the validation request with a 304. In that case (that is whenever "r->headers_out = ap_cache_cacheable_headers_out(r)" is executed in cache_save_filter), the original response headers concerned by "no-cache=" and/or "private=" won't be stored in the cache (legitimately), but they won't be forwarded to the client either. The same arise for the headers specified with the CacheIgnoreHeaders directive, but that was already the case before your patch(es). Finally, the macro CACHE_SEPARATOR is defined as ", " (with 3 spaces), I guess some tab might have been expanded in there... -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org For additional commands, e-mail: bugs-h...@httpd.apache.org
