Skip to content
This repository has been archived by the owner on Jul 11, 2023. It is now read-only.

fix(client) ensure validTtl override does not interfere with TTL of #134

Merged
merged 2 commits into from Jul 6, 2021

Conversation

dndx
Copy link
Member

@dndx dndx commented Jul 6, 2021

entries from hosts files

See: Kong/kong#7444 for bug report

The validTtl setting forcibly overwrites TTL inside the cacheinsert
function. However, this inadvertently overrides the TTL of hosts file
entries as well so that they may expire prematurely, causing resolving
failures later.

This PR changes so that validTtl will only be enabled after all
entries from hosts file are inserted.

entries from hosts files

See: Kong/kong#7444 for bug report

The `validTtl` setting forcibly overwrites TTL inside the `cacheinsert`
function. However, this inadvertently overrides the TTL of hosts file
entries as well so that they may expire prematurely, causing resolving
failures later.

This PR changes so that `validTtl` will only be enabled after all
entries from hosts file are inserted.
@Tieske Tieske merged commit 966b794 into master Jul 6, 2021
@Tieske Tieske deleted the fix/hosts_ttl branch July 6, 2021 09:52
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants