Skip to content

OTR_CLEAN_AGE default not correctly handled #500

@ckrey

Description

@ckrey

Feature introduced with #447 in version 0.9.8

If OTR_CLEAN_AGE is not specified (default = 0) or explicitly set to zero, the cache entries are always considered out of date, which leads to unintended reverse geo queries.

The cache is effectively invalidated 😭

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions