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 wrote:
> Could we also make the removal optional? It would be nice to be able
> to pass it down the heirarchy.
>
> On Tue
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 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_L
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 head
