The presence of the X-Debug header should not affect the cache key, unless it's done deliberately (e.g. via the cachekey plugin).
On Tue, Jul 10, 2018 at 2:26 PM Miles Libbey <mlib...@apache.org> wrote: > Could we also make the removal optional? It would be nice to be able > to pass it down the heirarchy. > > On Tue, Jul 10, 2018 at 12:19 PM, Walt Karas <wka...@oath.com.invalid> > wrote: > > For the xdebug plugin, does anybody object if I move the removal of > > the x-debug header field from the READ_RESPONSE_HDR_HOOK to the > > CACHE_LOOKUP_COMPLETE_HOOK? There's an Oath internal plugin that runs > > on the POST_REMAP_HOOK that needs to see whether x-debug is present or > > not. If the x-debug header is not removed prior to cache lookup, can > > it affect the cache key (he asked, thinking it would be crazy if the > > answer is yes but fearing it may be yes anyway)? > -- *Beware the fisherman who's casting out his line in to a dried up riverbed.* *Oh don't try to tell him 'cause he won't believe. Throw some bread to the ducks instead.* *It's easier that way. *- Genesis : Duke : VI 25-28
