How to remove listening port (5443) and protocol scheme (http/https) from the cache_key when it is not regular port while preserving the hostname? about cache-handler

[Zerorigin]

My idea is to add disable_proto and disable_port to the cache_keys block and move ttl and stale into the cache_keys to configure them.

This simplifies cache configuration for different static file types while improving cache efficiency.

[Zerorigin]

Additionally, the subcommand hide just hides the key value and does not remove the headers (Age and Cache-Status), which is slightly different than expected, and should perhaps be broken down into hide key, hide header, and hide off, which would make it easier for users who want to remove the headers.

[darkweak]

Hello @Zerorigin, I can add more directive to enable/disable the key. Btw I could add a TTL and stale directive to the cache_key block to be able to override the values. What do you think?

[Zerorigin]

Hello @Zerorigin, I can add more directive to enable/disable the key. Btw I could add a TTL and stale directive to the cache_key block to be able to override the values. What do you think?

This is great, just what I need.

[darkweak]

@Zerorigin in the next release you'll be able to create your own key template. e.g.

key {
    template "{host}-something-constant-{method} other {query}"
}

[darkweak]

And I still have to implement the TTL and stale directly in the cache_keys.

[Zerorigin]

@Zerorigin in the next release you'll be able to create your own key template. e.g.

key {
    template "{host}-something-constant-{method} other {query}"
}

The rest isn't urgent. 😄
Thanks for your hard work. ❤️